Hi, On Tue, 27 Feb 2007, Bill Lear wrote: > On Tuesday, February 27, 2007 at 21:22:31 (+0100) Johannes Schindelin writes: > > > Basically, shallow clones cut off branches at some point, even if > > those commits have references to their parents. > > Ah, so a sort of temporal surgery. > > I don't think this will help, and I don't think this is a unique git > issue, either. It happens with any system, I would think. > > Let's say I have 6 code repos on my system and one data repo. If I make > changes in one of my code repos that requires a test data change, I have > to move to my test data repo, make the change there, and commit there. > Then, back in my code repo, I commit also. > > Now, instead of one tidy package (a commit) that holds code and test > together in a coherent package, I have two separate commits in two repos > that now have to be coordinated. Imagine I do more changes in similar > fashion, and others do as well. Now our lead of the QA department is > pulling his hair out, trying to figure out which commits in the data > directory match those in the code directory so he can do regressions > properly. So, it is _not_ a transport question. Why not reference the commit name (the SHA1) of the commit changing behaviour in the commit of the test repo? Like: if abcdef0123 changes a certain output format, and this is expected, fix the test, and include a line "Reference-Commit: abcdef0123" in the test repo. This could even be done automatically by a simple script to commit changes after fixing an issue both in the source _and_ test repo... Ciao, Dscho - 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