FreeTDS Development Group

[Frediano Ziglio <freddy77 AT gmail.com>]

Il 03 aprile 2012 03:28, Craig A. Berry <craigberry AT mac.com> ha scritto:
> [trying this one again too after being "enqueued and undeliverable for 4 
> days"]
>
> Begin forwarded message:
>
>> From: "Craig A. Berry" <craigberry AT mac.com>
>> Subject: Re: [freetds] git advice
>> Date: March 28, 2012 7:38:47 PM CDT
>> To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
>>
>>
>> On Mar 27, 2012, at 9:00 PM, James K. Lowden wrote:
>>
>>> On Tue, 27 Mar 2012 21:30:55 -0400
>>> "James K. Lowden" <jklowden AT freetds.org> wrote:
>>>
>>>> Now we see this:
>>>>
>>>> $ git branch
>>>> * Branch-0_91
>>>> master
>>> ...
>>>> $ git describe --tags
>>>> branch-0_91-49-g4f40228
>>>
>>> but in master
>>>
>>> $ git describe  --tags
>>> branch-0_91-295-g9bfd5a7
>>>
>>> $ git branch
>>> * master
>>>
>>> :-(
>>>
>>
>> In the 0_91 branch you're 49 commits after the branch-0_91 tag and in 
>> master you're 295 commits after it.  There are no tags in master pointing 
>> to any commits later than the 0.91 release.  One way to handle this would 
>> be to immediately tag the first commit on master after the 0.91 release 
>> with something like devel-0.92.  Another way is to always extract the 
>> branch name and ignore the tag name, but then you have to be careful about 
>> any intermediate tags during the development cycle.
>>
>>

Moved branch-0_91 tag and created a branch-0_92 tag

Frediano