On Mon, 3 Nov 2008, Daniel Pittman wrote: >> I have also been thinking of using git, but that would be quite >> involved (every machine is a branch, give the user the possibility to >> merge the branch at a latter time). > > That would require some significant changes to git to allow pruning > revisions out of the history, or manual commits, either of which has > some nasty failure modes, I would have thought.
look at git filter-branch it allows you to process a repository, creating a new one that doesn't have things that were in the old one. the problem is that it is effectivly a new repository, so if people are cloning from you they will need to re-clone (and obviously, you cna't filter things out of their copy) this is used for things like when a company has been using git internally, then wants to clean up the prepository before making it public (eliminate inappropriate files from the repository, etc) or in a case where a person starts with git, then realizes many commits later that they should have created a .gitignore file to avoid putting things into the repository in the first place (which I have been guilty of on my internal projects) David Lang P.S. in another message on this thread the linux LVM snapshots were dismissed as close to worthless, I'd like to hear more about what the problems are _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
