From: Jason Merrill <jason@redhat.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Development <gcc@gcc.gnu.org>,
Overseers mailing list <overseers@sourceware.org>,
"Frank Ch. Eigler" <fche@elastic.org>
Subject: Re: origin/trunk branch - who added it?
Date: Fri, 23 Apr 2021 15:52:28 -0400 [thread overview]
Message-ID: <CADzB+2kcje1EicJYpbjhgxmvNJjTPfOov_EQMNVM+08saySKNw@mail.gmail.com> (raw)
In-Reply-To: <2544858b-654e-9efb-2ac5-ac8c37b1c6be@suse.cz>
On Fri, Apr 23, 2021 at 5:13 AM Martin Liška <mliska@suse.cz> wrote:
>
> Few weeks ago, I noticed we have a new remote branch that follows origin/master:
> https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/heads/trunk
>
> Do we know who added it? And what was the motivation?
I did; I've always preferred that name (for metaphorical consistency
with 'branch'), and there's been a wider move away from 'master' in
git repositories. I figured we could support both easily enough, but
the hooks still need updating to treat 'trunk' the same way they treat
'master'.
Jason
prev parent reply other threads:[~2021-04-23 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 9:13 Martin Liška
2021-04-23 19:52 ` Jason Merrill [this message]
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=CADzB+2kcje1EicJYpbjhgxmvNJjTPfOov_EQMNVM+08saySKNw@mail.gmail.com \
--to=jason@redhat.com \
--cc=fche@elastic.org \
--cc=gcc@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=overseers@sourceware.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).