From: Jonathan Wakely <jwakely@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Sam James <sam@gentoo.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/4] maintainer-scripts/gcc_release: create index between snapshots <-> commits
Date: Thu, 2 Nov 2023 10:25:47 +0000 [thread overview]
Message-ID: <CACb0b4koN59P-nYuxe4X1Oi7RsZ6kY=9KQVA8UtzpF0phHNpqw@mail.gmail.com> (raw)
In-Reply-To: <87r0l81ms0.fsf@igel.home>
On Thu, 2 Nov 2023 at 10:23, Andreas Schwab wrote:
>
> On Nov 02 2023, Jonathan Wakely wrote:
>
> > Git tags are cheap, but I can imagine a concern about hundreds of new
> > tags "littering" the output of 'git tag -l'. I don't _think_ you can
> > put tags under an alternative ref that isn't fetched by default (as we
> > do with refs/users and refs/vendor). I think tags have to go under
> > refs/tags. But grep -v could be used to filter out snapshot tags
> > easily.
>
> There is no inherent limitation on publishing tags outside of refs/tags,
> to make them invisible by git tag. There are already existing examples
> of tags residing under various refs/users and refs/vendors namespaces.
Ah, good to know, thanks.
So then there's no reason that snapshots would have to clutter up the
list of default tags for anybody who isn't interested in them.
next prev parent reply other threads:[~2023-11-02 10:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 8:39 [PATCH 1/4] contrib: add generate_snapshot_index.py Sam James
2023-11-02 8:39 ` [PATCH 2/4] maintainer-scripts/gcc_release: create index between snapshots <-> commits Sam James
2023-11-02 9:07 ` Jonathan Wakely
2023-11-02 10:18 ` Andreas Schwab
2023-11-02 10:25 ` Jonathan Wakely [this message]
2023-11-02 22:18 ` rep.dot.nop
2023-11-02 8:39 ` [PATCH 3/4] maintainer-scripts/gcc_release: use HTTPS for links Sam James
2023-11-02 18:59 ` Joseph Myers
2023-11-02 8:39 ` [PATCH 4/4] maintainer-scripts/gcc_release: cleanup whitespace Sam James
2023-11-02 19:00 ` Joseph Myers
2023-11-10 23:35 ` Sam James
2023-11-14 0:21 ` Joseph Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACb0b4koN59P-nYuxe4X1Oi7RsZ6kY=9KQVA8UtzpF0phHNpqw@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sam@gentoo.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).