public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc@gcc.gnu.org, Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++@gcc.gnu.org
Subject: Renaming git master?
Date: Sun, 15 Jan 2023 22:22:22 +0100 (CET)	[thread overview]
Message-ID: <768dbbdd-25b3-f0e5-2078-609863652e4a@pfeifer.com> (raw)
In-Reply-To: <20210329131520.GZ3008@redhat.com>

[ gcc-patches -> gcc ]

On Mon, 29 Mar 2021, Jonathan Wakely wrote:
>> [LLVM] renamed the 'master' branch. I'll adjust the link tomorrow.
> Done by this patch, pushed to master (which I think we should rename).

Did I miss any discussions? Our documentation at 
  https://gcc.gnu.org/git.html
still refers to master (though, probably dating back to the SVN days there 
are quite a number of references to trunk, too).

`git branch -l` shows 
  master
  remotes/origin/HEAD -> origin/master
  remotes/origin/trunk


1. Is there something we may want to adjust in the Git repository?

2. How about https://gcc.gnu.org/git.html ? 

   (If someone tells me what to use instead of "master" I can propose a 
   patch.)
 
Gerald

       reply	other threads:[~2023-01-15 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4790336d-cffc-342f-47e0-7c7280fcda17@pfeifer.com>
     [not found] ` <CAH6eHdR-SgF3KNAfqxDZrE6ny2gGr4U-VHFJ3=R83ktXweJgtg@mail.gmail.com>
     [not found]   ` <20210329131520.GZ3008@redhat.com>
2023-01-15 21:22     ` Gerald Pfeifer [this message]
2023-01-15 22:44       ` Jonathan Wakely
2023-01-16 18:35       ` 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=768dbbdd-25b3-f0e5-2078-609863652e4a@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.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).