From: Thien-Thi Nguyen <ttn@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs branches in git
Date: Mon, 17 Feb 2014 13:51:50 +0100 [thread overview]
Message-ID: <877g8t9a1l.fsf@zigzag.favinet> (raw)
In-Reply-To: <53017273.10304@yandex.ru> (Dmitry Gutov's message of "Mon, 17 Feb 2014 04:22:43 +0200")
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
() Dmitry Gutov <dgutov@yandex.ru>
() Mon, 17 Feb 2014 04:22:43 +0200
> OK, it might not have justification, but it isn't arbitrary. What
> is the justification for *not* [using "master" for named releases]?
As far as I'm concerned, it subverts the meaning of "master".
That's just one opinion, though.
Well, it's possible to have a repo w/o "master" (e.g., all my local
repos), so there is really no inherent meaning tied to that branch name.
I prefer branch discipline ((re-)naming, operation, role in the DAG) to
be explicit, and like the scheme on the referenced page very much, the
only exception being the name "master". If that were renamed "public"
or "archive", for example, then it would be perfect (IMHO). This way,
the name reflects the function, and we sidestep the potential confusion
of "conventional meanings" (insert "so many standards" smirk, here).
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-02-17 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 4:50 Emacs branches in git Bill Wohler
2014-02-16 5:01 ` Dmitry Gutov
2014-02-16 20:11 ` Bill Wohler
2014-02-16 20:17 ` David Kastrup
2014-02-16 22:30 ` Bill Wohler
2014-02-16 23:53 ` Dmitry Gutov
2014-02-17 0:36 ` Bill Wohler
2014-02-17 2:22 ` Dmitry Gutov
2014-02-17 9:11 ` Andreas Schwab
2014-02-17 12:51 ` Thien-Thi Nguyen [this message]
2014-02-17 22:51 ` Xue Fuqiao
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=877g8t9a1l.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).