Re: GIT tutorials (was: Re: Fix bug in GSM MAP, have problems with GIT)

[Evan Huus <eapache () gmail com>]

On Tue, Mar 11, 2014 at 4:55 PM, Guy Harris <guy () alum mit edu> wrote:
> On Mar 11, 2014, at 1:42 PM, Graham Bloice <graham.bloice () trihedral com> 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
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe