Hello group, I've been using git on a few different projects over the last couple of months, and as a former svn user I really like it. Recently, I've been using it as an 'electronic lab notebook' for an empirical project. My workflow looks like this: 1. Start with the stable code base on head 2. Create and change to branch 'Experiment123' 3. Make some changes 4. Run the program, which generates a giant (10MB-4G) output text file, Experiment123.log. Update my LabNotebook.txt file. 5. Were the new changes helpful? 5.yes: Bzip Experiment123.log, and commit it on the branch. Merge the Experiment123 branch to head and goto 1. 5.no: Bzip Experiment123.log, and commit it on the branch. Merge LabNotebook.txt and Experiment123.log back to head. Switch back to head and goto 1. The thing is, Experiment123.log is going to be very similar to Experiment122.log and Experiment124.log except for a few details. My understanding is that git is great at compressing groups of files like this, is that correct? Should I not be bzipping them myself? On the other hand, I don't want HEAD to contain hundreds of gigs of uncompressed files that bzip down to only a few hundred megs. Any thoughts on the workflow itself would also be very welcome. -- 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