Wireshark-dev: Re: [Wireshark-dev] GIT tutorials (was: Re: Fix bug in GSM MAP, have problems wi
From: Evan Huus <[email protected]>
Date: Tue, 11 Mar 2014 16:58:05 -0400
On Tue, Mar 11, 2014 at 4:55 PM, Guy Harris <[email protected]> wrote:
>
> On Mar 11, 2014, at 1:42 PM, Graham Bloice <[email protected]> wrote:
>
>> In any case I don't think this fulfils the initial question.  Previously we could say to users that an issue was fixed in svn r nnnn and they would "know" that any rev later than that was good.  I don't understand how they can "know" that with a SHA of the latest master commit | merge.
>
> That'd require a commit identifier where, on any given branch in the official repository, given the identifiers for two commits, it's easy to determine which commit is later.  That's true of SVN revision numbers, as they're time-ordered, but it's not true of SHA hashes for Git commits.

Git will give you the answer (several options are given at [1]) but
the SHAs themselves are not comparable.

[1] https://stackoverflow.com/questions/18345157/how-can-i-tell-if-one-commit-is-an-ancestor-of-another-commit-or-vice-versa