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

[Alexis La Goutte <alexis.lagoutte () gmail com>]

On Tue, Mar 11, 2014 at 7:01 PM, Roland Knall <rknall () gmail com> wrote:
> On Tue, Mar 11, 2014 at 6:47 PM, Hadriel Kaplan
> <hadriel.kaplan () oracle com> wrote:
> > > 4) How do you know if someone has a fix or not?  With subversion, they'd
> > > indicate they're running svn r51234, for example, and then you could tell
> > > them that they need to update to at least r52345.  With git, how does this
> > > work with hashes?
> >
> > That would be good to know - because so far it seems people've been using the first ~6 characters of the commit 
> > hashes, but I'm not sure if that's right or not.
>
> That is in general the git method. Better to use the first 12, but the
> general idea stays the same. But I would rather suggest using the
> gerrit change-ids, as those are universal. Git commit ids differ
> between different people (each clone may create their one), but
> change-ids stay identical.

For Wireshark build ( http://www.wireshark.org/download/automated )
The file contains the number of commit from "start of new branch"


> - Roland
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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