public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: newlib-cygwin.git repository: Switching "master" to "main"
Date: Fri, 13 Jan 2023 15:44:48 +0100	[thread overview]
Message-ID: <Y8FuYLAyk/rlhzcc@calimero.vinschen.de> (raw)
In-Reply-To: <32aca832-3e93-d988-7636-7d4853512610@gmx.com>

On Jan 13 14:20, Sam Edge via Cygwin wrote:
> On 13/01/2023 11:55, Corinna Vinschen via Cygwin wrote:
> > Hey folks,
> >
> > In the light of recent discussions, and following other projects already
> > having done this step, we changed the name of the "master" branch in
> > the newlib-cygwin.git upstream repository to "main".
> >
> > If you fetched from upstream in the last two days, you might already
> > have noticed that an "origin/main" branch suddenly showed up, but your
> > "master" branch still worked as before.
> >
> > The reason is that we also added a symbolic reference upstream, so that
> > "origin/master" points to "origin/main".  Both "branches" are now
> > constantly kept in sync upstream.
> >
> > Therefore, you can continue your work on "master" without disruption,
> > if you prefer to do so.
> >
> > However, on the client side, the "master" and "main" branches are
> > treated as two distinct branches.  If you work on your local "main"
> > clone and commit a patch, it's not keeping your local "master" branch in
> > sync.  After pushing your change upstream, though, the upstream idea of
> > "main" and "master" is, again, the same.  After fetching from upstream,
> > the patch will show up in both tracking branches, "origin/main" as well
> > as "origin/master", so pulling on both local branches will show the same
> > tree.
> >
> > Having said that.  Ideally you only use one of the branches locally
> > to avoid any confusion:
> >
> > - If you prefer to work in "master", just continue to do so and don't
> >   create a local "main" branch tracking "origin/main".
> >
> > - If you prefer to work in "main", checkout "origin/main" as "main" and
> >   delete your local "master" branch.
> >
> >
> > Have fun,
> > Corinna
> >
> >
> 
> While I can understand sensitivity over the word 'slave' this is taking
> things
> too far in my opinion. I just conducted a quick poll of my Afro-Caribbean &
> other non-Caucasian workmates who all express the same sentiment.
> [...]
> Well, it's a fait accompli on the Cygwin repos.

That's why we chose the symbolic ref solution.  You can use both in
future, whichever you like more.


Corinna

  reply	other threads:[~2023-01-13 14:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 11:55 Corinna Vinschen
2023-01-13 12:10 ` Corinna Vinschen
2023-01-13 14:20 ` Sam Edge
2023-01-13 14:44   ` Corinna Vinschen [this message]
2023-01-13 19:23 ` Mike Frysinger
2023-01-13 19:57   ` Adam Dinwoodie
2023-01-13 20:16     ` Dave McGuire
2023-01-13 23:29       ` Eliot Moss

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=Y8FuYLAyk/rlhzcc@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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).