[haiku-development] Re: Git/Hg: some speed tests

  • From: Niels Sascha Reedijk <niels.reedijk@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Thu, 5 May 2011 07:12:28 +0200

Hi,

2011/5/5 Ingo Weinhold <ingo_weinhold@xxxxxx>:
> On Thu, 05 May 2011 01:44:43 +0200 Oliver Tappe <zooey@xxxxxxxxxxxxxxx> wrote:
>> We could tag the very first changeset of every branch (i.e. in master and
>> every release branch) and then use 'git describe' to work out a revision
>> descriptor that would look like this:
>>
>>     master-39148-g206031c               [in the master branch]
>>     r1a3pre-21-g1234567               [in the r1a3 release branch, before
>>                                        the release]
>>     r1a3-4-g1234567                   [in the r1a3 release branch, after
>>                                        the release]
>>
>> The numbers in the second column always indicate the distance the specific
>> revision has from the tag given in the first column (the third column
>> being
>> git's short hash for the changeset).
>>
>> This would require only one tag for each branch plus one per release.
>>
>> Additionally, incorporating these descriptors in AboutSystem would clearly
>> indicate "foreign" builds (e.g. done from a feature branch available on
>> github/gitorious), as those descriptors wouldn't match any in the central
>> master.
>
> Maybe I misunderstand something, but when I clone the haiku-central master 
> master-39148-g206031c and make three local commits I get something like 
> master-39151-g0329483, right? So that doesn't really tell us which 
> haiku-central version my version is based on -- it could just as well be 5 
> local commits after master-39146-... or 10000 local commits after 
> master-29151-....

Just another note: the first identifier in the string is the nearest
tag name, not the branch name.

N>

Other related posts: