llvm dev - Oct 2019 - Tag for using git describe on master

As first discussed in the giant "New LLVM git repository conversion
prototype" thread, I've pushed a git tag that allows git-describe to
be used for generating human readable commit names on master.

The tag is "llvmorg-10-init", to be interpreted as "the initial
commit
with major version number 10". The idea is to add similar tags along
with future version bumps.

git describe generates a name like this:

$ git describe a4783ef
llvmorg-10-init-8348-ga4783ef58d3

Where "llvmorg-10-init" is the tag name, 8348 is the number of commits
since the tag (yay, monotonically incrementing commit numbers), and
"a4783ef58d3" is the hash with "g" as a magic prefix to
indicate it's
a git hash.

The name can be used to refer to commits directly (git only looks at
the hash after the "g"):

$ git show llvmorg-10-init-8348-ga4783ef58d3 -s --oneline
a4783ef58d3 [Alignment][NFC] getMemoryOpCost uses MaybeAlign


Thanks,
Hans

Thanks Hans!

Is this something that we can document somewhere? (especially if we will
continue to maintain / create tags with each branching).

-- 
Mehdi


On Fri, Oct 25, 2019 at 1:06 PM Hans Wennborg via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> As first discussed in the giant "New LLVM git repository conversion
> prototype" thread, I've pushed a git tag that allows git-describe
to
> be used for generating human readable commit names on master.
>
> The tag is "llvmorg-10-init", to be interpreted as "the
initial commit
> with major version number 10". The idea is to add similar tags along
> with future version bumps.
>
> git describe generates a name like this:
>
> $ git describe a4783ef
> llvmorg-10-init-8348-ga4783ef58d3
>
> Where "llvmorg-10-init" is the tag name, 8348 is the number of
commits
> since the tag (yay, monotonically incrementing commit numbers), and
> "a4783ef58d3" is the hash with "g" as a magic prefix to
indicate it's
> a git hash.
>
> The name can be used to refer to commits directly (git only looks at
> the hash after the "g"):
>
> $ git show llvmorg-10-init-8348-ga4783ef58d3 -s --oneline
> a4783ef58d3 [Alignment][NFC] getMemoryOpCost uses MaybeAlign
>
>
> Thanks,
> Hans
> _______________________________________________
> 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/20191026/b3c37525/attachment.html>

Sure, the question is where :-) Do we have a doc describing our git
setup somewhere?

(Currently traveling, slow to reply.)

On Sat, Oct 26, 2019 at 9:45 AM Mehdi AMINI <joker.eph at gmail.com>
wrote:
>
> Thanks Hans!
>
> Is this something that we can document somewhere? (especially if we will
continue to maintain / create tags with each branching).
>
> --
> Mehdi
>
>
> On Fri, Oct 25, 2019 at 1:06 PM Hans Wennborg via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
>>
>> As first discussed in the giant "New LLVM git repository
conversion
>> prototype" thread, I've pushed a git tag that allows
git-describe to
>> be used for generating human readable commit names on master.
>>
>> The tag is "llvmorg-10-init", to be interpreted as "the
initial commit
>> with major version number 10". The idea is to add similar tags
along
>> with future version bumps.
>>
>> git describe generates a name like this:
>>
>> $ git describe a4783ef
>> llvmorg-10-init-8348-ga4783ef58d3
>>
>> Where "llvmorg-10-init" is the tag name, 8348 is the number
of commits
>> since the tag (yay, monotonically incrementing commit numbers), and
>> "a4783ef58d3" is the hash with "g" as a magic
prefix to indicate it's
>> a git hash.
>>
>> The name can be used to refer to commits directly (git only looks at
>> the hash after the "g"):
>>
>> $ git show llvmorg-10-init-8348-ga4783ef58d3 -s --oneline
>> a4783ef58d3 [Alignment][NFC] getMemoryOpCost uses MaybeAlign
>>
>>
>> Thanks,
>> Hans
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

Will the use of `git describe` output become required anywhere? Or will normal
git hashes always be acceptable? I ask because people sometimes pass --no-tags
to git-clone, etc.
> On Oct 25, 2019, at 11:06 PM, Hans Wennborg via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> As first discussed in the giant "New LLVM git repository conversion
> prototype" thread, I've pushed a git tag that allows git-describe
to
> be used for generating human readable commit names on master.
> 
> The tag is "llvmorg-10-init", to be interpreted as "the
initial commit
> with major version number 10". The idea is to add similar tags along
> with future version bumps.
> 
> git describe generates a name like this:
> 
> $ git describe a4783ef
> llvmorg-10-init-8348-ga4783ef58d3
> 
> Where "llvmorg-10-init" is the tag name, 8348 is the number of
commits
> since the tag (yay, monotonically incrementing commit numbers), and
> "a4783ef58d3" is the hash with "g" as a magic prefix to
indicate it's
> a git hash.
> 
> The name can be used to refer to commits directly (git only looks at
> the hash after the "g"):
> 
> $ git show llvmorg-10-init-8348-ga4783ef58d3 -s --oneline
> a4783ef58d3 [Alignment][NFC] getMemoryOpCost uses MaybeAlign
> 
> 
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

I don't imagine it would become required anywhere. Git hashes are the
source of truth.

On Mon, Oct 28, 2019 at 2:50 PM David Zarzycki <dave at znu.io>
wrote:
>
> Will the use of `git describe` output become required anywhere? Or will
normal git hashes always be acceptable? I ask because people sometimes pass
--no-tags to git-clone, etc.
>
> > On Oct 25, 2019, at 11:06 PM, Hans Wennborg via llvm-dev <llvm-dev
at lists.llvm.org> wrote:
> >
> > As first discussed in the giant "New LLVM git repository
conversion
> > prototype" thread, I've pushed a git tag that allows
git-describe to
> > be used for generating human readable commit names on master.
> >
> > The tag is "llvmorg-10-init", to be interpreted as "the
initial commit
> > with major version number 10". The idea is to add similar tags
along
> > with future version bumps.
> >
> > git describe generates a name like this:
> >
> > $ git describe a4783ef
> > llvmorg-10-init-8348-ga4783ef58d3
> >
> > Where "llvmorg-10-init" is the tag name, 8348 is the number
of commits
> > since the tag (yay, monotonically incrementing commit numbers), and
> > "a4783ef58d3" is the hash with "g" as a magic
prefix to indicate it's
> > a git hash.
> >
> > The name can be used to refer to commits directly (git only looks at
> > the hash after the "g"):
> >
> > $ git show llvmorg-10-init-8348-ga4783ef58d3 -s --oneline
> > a4783ef58d3 [Alignment][NFC] getMemoryOpCost uses MaybeAlign
> >
> >
> > Thanks,
> > Hans
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>