Alexandre Oliva <lxoliva@xxxxxxxxx> wrote > I need to be able to maintain and publish a modified repository, that > filters out the unwanted portions, but still be able to pull changes > from the upstream repository. Have you tried something with "git filter-branch"? I have never tried something like this but I think it is possible to automate a process to (1) pull the changes from the origin into a complete clone, (2) branch from the HEAD and run "filter-branch" with a customized script to create a temporary sanitized branch, (3) merge this temporary branch into a complete sanitized branch, (4) record all the branchpoints, sparing the next iteration from running through all the history again, and, (5) push the sanitized branch somewhere. Of course, this approach creates a complete nightmare with the integration, testing, and code attribution: it changes the SHA1s, invalidates signed tags, forces the use of patches instead of pull requests to the upstream contributions, may taint the validity of the commit messages and authorship, etc. Publishing edited commits seems a delicate subject for me -- your "filter-branch" script should mark their commit messages as such. Att. -- Alexandre Erwin Ittner - alexandre@xxxxxxxxxxxxx OpenPGP pubkey 0x0041A1FB @ http://pgp.mit.edu -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html