Joerg Sonnenberger <joerg at britannica.bec.de> writes:> The problem is answering the question of "do I have it or not". Linear > version numbers are much nicer for that.In the presence of branches, the version number alone doesn't answer this question, because the commit may be more recent than your HEAD, but in another branch. git branch --contains <sha1>, on the other hand, will tell you. -- Matthieu Moy http://www-verimag.imag.fr/~moy/
On Jul 21, 2011, at 8:22 AM, Matthieu Moy wrote:> Joerg Sonnenberger <joerg at britannica.bec.de> writes: >> The problem is answering the question of "do I have it or not". Linear >> version numbers are much nicer for that. > > In the presence of branches, the version number alone doesn't answer > this question, because the commit may be more recent than your HEAD, but > in another branch. > > git branch --contains <sha1>, on the other hand, will tell you.Of course, this doesn't actually help if you've cherry-picked commits over to your branch (e.g. because it's a release branch). I agree with Joerg; it's a serious regression, but not a show-stopper. John.
John McCall <rjmccall at apple.com> writes:>> git branch --contains <sha1>, on the other hand, will tell you. > > Of course, this doesn't actually help if you've cherry-picked commits > over to your branch (e.g. because it's a release branch).How is that different from SVN? If revision 1234 fixes a bug is some branch, and the last revision in your trunk is 2345, can you tell whether your trunk has this bugfix applied by looking at revision numbers? -- Matthieu Moy http://www-verimag.imag.fr/~moy/