From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: generating a git repo: main instead of master
Date: Sun, 13 Nov 2022 10:25:55 +0200 [thread overview]
Message-ID: <83r0y7l0q4.fsf@gnu.org> (raw)
In-Reply-To: <83sfinl0sw.fsf@gnu.org> (message from Eli Zaretskii on Sun, 13 Nov 2022 10:24:15 +0200)
> Date: Sun, 13 Nov 2022 10:24:15 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> If you want "master" to be the default
^^^^^^^^
Sorry, this was supposed to be "main".
next prev parent reply other threads:[~2022-11-13 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 8:03 generating a git repo: main instead of master Uwe Brauer
2022-11-13 8:24 ` Eli Zaretskii
2022-11-13 8:25 ` Eli Zaretskii [this message]
2022-11-13 8:38 ` Uwe Brauer
2022-11-13 9:27 ` tomas
2022-11-13 14:50 ` Björn Bidar
2022-11-13 8:26 ` Peter Hardy
2022-11-13 8:32 ` Teemu Likonen
2022-11-13 8:33 ` tomas
2022-11-13 8:43 ` Uwe Brauer
2022-11-13 9:22 ` tomas
2022-11-13 9:31 ` Jean Louis
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r0y7l0q4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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).