llvm dev - Oct 2019 - mini RFC: adding a tag for the SVN -> github migration

Proposal:

$ git tag -a r375505 186155b89c2d2a2f62337081e3ca15f676c9434b -m "Last SVN
commit before switchover to github."
$ git push origin r375505

Why?

This makes "git describe" produce usable linear revision numbers that
are a
natural continuation of the SVN revision numbering. For example, a git
describe on HEAD from earlier today gives:

$ git describe
r375505-115-g9b8dd004034

(That is: r375505 plus 115 git commits = 9b8dd004034)

This isn't intended to be an official revision number, nor a long-term
solution to the numbering problem, but seems useful in the short term.

Thoughts?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20191024/02b4517e/attachment.html>

I really don't like that....I'd much prefer to resurrect the previous
discussion about tagging master after each release branch-point. Which I
*think* was generally agreed upon, except for a debate about what to CALL
those tags.

E.g., if we called `git merge-base origin/release/9.x origin/master`
"10_dev", then

$ git describe
10_dev-8276-g9671d1dc1764

On Thu, Oct 24, 2019 at 7:00 PM Richard Smith via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Proposal:
>
> $ git tag -a r375505 186155b89c2d2a2f62337081e3ca15f676c9434b -m "Last
SVN
> commit before switchover to github."
> $ git push origin r375505
>
> Why?
>
> This makes "git describe" produce usable linear revision numbers
that are
> a natural continuation of the SVN revision numbering. For example, a git
> describe on HEAD from earlier today gives:
>
> $ git describe
> r375505-115-g9b8dd004034
>
> (That is: r375505 plus 115 git commits = 9b8dd004034)
>
> This isn't intended to be an official revision number, nor a long-term
> solution to the numbering problem, but seems useful in the short term.
>
> Thoughts?
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20191024/a5ccd310/attachment-0001.html>

As an end to that debate, I added a "llvmorg-10-init" tag just now,
see http://lists.llvm.org/pipermail/llvm-dev/2019-October/136188.html

Richard, does that address your use case?

On Thu, Oct 24, 2019 at 7:59 PM James Y Knight via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> I really don't like that....I'd much prefer to resurrect the
previous discussion about tagging master after each release branch-point. Which
I think was generally agreed upon, except for a debate about what to CALL those
tags.
>
> E.g., if we called `git merge-base origin/release/9.x origin/master`
"10_dev", then
>
> $ git describe
> 10_dev-8276-g9671d1dc1764
>
> On Thu, Oct 24, 2019 at 7:00 PM Richard Smith via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
>>
>> Proposal:
>>
>> $ git tag -a r375505 186155b89c2d2a2f62337081e3ca15f676c9434b -m
"Last SVN commit before switchover to github."
>> $ git push origin r375505
>>
>> Why?
>>
>> This makes "git describe" produce usable linear revision
numbers that are a natural continuation of the SVN revision numbering. For
example, a git describe on HEAD from earlier today gives:
>>
>> $ git describe
>> r375505-115-g9b8dd004034
>>
>> (That is: r375505 plus 115 git commits = 9b8dd004034)
>>
>> This isn't intended to be an official revision number, nor a
long-term solution to the numbering problem, but seems useful in the short term.
>>
>> Thoughts?
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev