[llvm-dev] New LLVM git repository conversion prototype

via llvm-dev llvm-dev at lists.llvm.org
Thu Dec 13 13:59:33 PST 2018

> -----Original Message-----
> From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of David
> Greene via llvm-dev
> Sent: Thursday, December 13, 2018 2:26 PM
> To: David Jones
> Cc: llvm-dev
> Subject: Re: [llvm-dev] New LLVM git repository conversion prototype
> David Jones via llvm-dev <llvm-dev at lists.llvm.org> writes:
> ...
> > For a development tag, we should probably try to keep it short,
> > simple, and obvious. After all, we're fundamentally talking about a
> > tag used for development, not releases; something short, like
> > "master-v8" would yield concise, obvious aliases like
> > "master-v8-1234-abcdef01". (Tags on release branches are a
> > fundamentally different matter, and could continue looking exactly
> > like they do today.)
> "master" could be confusing for downstream.  For example we have a setup
> where our development happens on "master" and we have a branch called
> "upstream_master" to pull from upstream.  It would be confusing to see a
> tag called "master" on a branch not named "master."

Same here. Our "master" is not the upstream "master."

> "v8.0.0-split/dev/branchpoint/whatever" could also be confusing to
> downstream as it could conflict with downstream named tags if their
> products happen to have version number conflicts.  Follwing Duncan's
> suggestion, would llvm.org-8.0.0-split (or suggest some other suffix)
> work?  I know it's longer but it would be unambiguous.
> "Duncan P. N. Exon Smith via llvm-dev" <llvm-dev at lists.llvm.org> writes:
> > I have a mild preference for "llvm.org-8.0.0" (instead of
> > "llvm-8.0.0"), since llvm.org is unambiguously a point of origin,
> > whereas "llvm" could just refer to the content. E.g., some downstreams
> > might package their product with the name "llvm".
> I have a slight preference for that too, for the same reasons.

Works for me.  We actually put both the upstream and local versions into
our release-branch names because we could never keep them straight.

More information about the llvm-dev mailing list