From: Juri Linkov <juri@linkov.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Emacs-Devel List <emacs-devel@gnu.org>,
Boruch Baum <boruch_baum@gmx.com>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: elpa.git and `new-master`
Date: Wed, 16 Dec 2020 22:41:24 +0200 [thread overview]
Message-ID: <87y2hxmtcr.fsf@mail.linkov.net> (raw)
In-Reply-To: <jwv8s9x4nzh.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 16 Dec 2020 13:24:35 -0500")
> I don't have a strong opinion on the specific color of this bikeshed
> ("master" is convenient because it's less work to implement, "trunk" is
> what I got used to back in Bzr days and what I thus keep using locally,
> but "main" is more meaningful (and "virtue signaling")).
>
> My original plan was to rename `new-master` to `master`, but I'd be
> happy to rename it to `main` instead.
For the sake of completion, either `master` or `main` is fine, but
please don't add both branches with the same prefix. For example,
I use completion on branch names all the time, and it's very convenient
to quickly type just `o TAB m TAB` or `o/m TAB` to complete the
`origin/master` branch. Having two branches with the same prefix `ma-`
would be a hassle.
next prev parent reply other threads:[~2020-12-16 20:41 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 6:47 elpa.git and `new-master` Boruch Baum
2020-12-16 7:38 ` Jean Louis
2020-12-16 8:24 ` Andreas Schwab
2020-12-16 9:31 ` Jean Louis
2020-12-16 9:59 ` Andreas Schwab
2020-12-16 8:49 ` Pankaj Jangid
2020-12-16 9:34 ` Jean Louis
2020-12-16 9:01 ` Alfred M. Szmidt
2020-12-16 12:29 ` Joost Kremers
2020-12-16 13:48 ` Jean Louis
2020-12-16 14:04 ` Lars Ingebrigtsen
2020-12-16 14:40 ` Jean Louis
2020-12-16 14:26 ` Stefan Monnier
2020-12-16 20:08 ` Stephen Leake
2020-12-17 3:58 ` Tim Landscheidt
2020-12-17 5:54 ` Richard Stallman
2020-12-17 8:25 ` Joost Kremers
2020-12-17 16:22 ` Stephen Leake
2020-12-18 5:48 ` Richard Stallman
2020-12-16 17:03 ` Clément Pit-Claudel
2020-12-16 9:03 ` Lars Ingebrigtsen
2020-12-16 10:19 ` Pankaj Jangid
2020-12-16 14:15 ` Boruch Baum
2020-12-16 13:48 ` Gregory Heytings via Emacs development discussions.
2020-12-16 13:53 ` Lars Ingebrigtsen
2020-12-16 14:43 ` Gregory Heytings via Emacs development discussions.
2020-12-16 15:24 ` Pankaj Jangid
2020-12-16 15:37 ` Jean Louis
2020-12-16 17:54 ` Alfred M. Szmidt
2020-12-16 16:23 ` Eli Zaretskii
2020-12-16 16:16 ` Dmitry Gutov
2020-12-16 18:24 ` Stefan Monnier
2020-12-16 18:46 ` Dmitry Gutov
2020-12-16 19:03 ` Boruch Baum
2020-12-16 19:06 ` Stefan Monnier
2020-12-16 19:21 ` Boruch Baum
2020-12-16 19:55 ` Stefan Monnier
2020-12-16 19:22 ` Andreas Schwab
2020-12-16 19:56 ` Stefan Monnier
2020-12-16 20:06 ` Andreas Schwab
2020-12-16 20:12 ` Boruch Baum
2020-12-16 20:19 ` Lars Ingebrigtsen
2020-12-16 21:16 ` Boruch Baum
2020-12-16 21:38 ` Stefan Monnier
2020-12-16 20:38 ` Stefan Monnier
2020-12-16 20:46 ` Stefan Monnier
2020-12-16 20:53 ` Dmitry Gutov
2020-12-16 21:09 ` Lars Ingebrigtsen
2020-12-16 21:34 ` Stefan Monnier
2020-12-17 0:11 ` Caio Henrique
2020-12-17 3:37 ` Eli Zaretskii
2020-12-17 8:15 ` Joost Kremers
2020-12-17 8:39 ` Tim Cross
2020-12-17 15:14 ` Stefan Monnier
2020-12-16 20:41 ` Juri Linkov [this message]
2020-12-16 21:24 ` Boruch Baum
-- strict thread matches above, loose matches on Subject: below --
2020-12-15 4:46 Stefan Monnier
2020-12-15 16:09 ` Eli Zaretskii
2020-12-15 16:53 ` Stefan Monnier
2020-12-15 18:24 ` Eli Zaretskii
2020-12-15 19:02 ` Stephen Leake
2020-12-15 19:16 ` Eli Zaretskii
2020-12-15 21:09 ` Dmitry Gutov
2020-12-15 21:33 ` Stefan Monnier
2020-12-16 15:36 ` Eli Zaretskii
2020-12-15 18:57 ` Stephen Leake
2020-12-15 21:35 ` Stefan Monnier
2020-12-16 5:43 ` Richard Stallman
2020-12-16 8:33 ` Tim Cross
2020-12-17 5:55 ` Richard Stallman
2020-12-16 9:00 ` Alfred M. Szmidt
2020-12-15 19:03 ` Stephen Leake
2020-12-15 21:43 ` Jonas Bernoulli
2020-12-15 22:34 ` Stefan Monnier
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=87y2hxmtcr.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=boruch_baum@gmx.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.