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

[Hadriel Kaplan <hadriel.kaplan () oracle com>]

On Mar 11, 2014, at 5:15 PM, Guy Harris <guy () alum mit edu> wrote:

> Perhaps we should have a page on some wireshark.org where a user can enter some identifier for an automated build and 
> an SHA hash for a commit and find out whether that build has that commit, and perhaps also say "take me to the latest 
> automated build for {pick your target for binary builds} that has this commit" (or fail if there's no such build yet).

Googling around a bit for this issue - because other apps must have this same problem and their users - shows people 
either creating a ton of tags, or scripting with the rev-list count to generate sequential numbers in their commits to 
master.

How did SVN deal with a rev number in older branches, when you either backported a change from a newer release or 
committed a change only to the older release?  Did it use the same rev number, or give it a new one? (ie, was it the 
same/shared numberspace?)

-hadriel

___________________________________________________________________________
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