Wireshark-dev: Re: [Wireshark-dev] GIT tutorials (was: Re: Fix bug in GSM MAP, have problems wi

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Tue, 11 Mar 2014 13:55:25 -0700
On Mar 11, 2014, at 1:42 PM, Graham Bloice <graham.bloice@xxxxxxxxxxxxx> 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.