git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] "master" should be treated no differently from any other branch
Date: Thu, 14 Dec 2006 16:25:07 +0000	[thread overview]
Message-ID: <200612141625.08485.andyparkins@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0612141627090.3635@wbgn013.biozentrum.uni-wuerzburg.de>

On Thursday 2006 December 14 15:29, Johannes Schindelin wrote:

> I do not agree. There is usually a principal branch, where you collect the
> topics, and you do want to treat that special. As for the name: better

While there might _usually_ be a principal branch; the special casing is 
_always_ hard coded.

> have a convention here than configurability. You would not want "git" to
> be called "guitar" for some users, just because they happen to like that
> name more, either, right?

You're correct; but we're talking about branch names not program names.  
Making "master" special rather than simply a default means git is dictating 
policy.  It isn't git's place to decide what my branches are called, 
especially as it is git itself that lets me choose freely to begin with.

Andy
-- 
Dr Andy Parkins, M Eng (hons), MIEE

  parent reply	other threads:[~2006-12-14 16:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14 15:19 [PATCH] "master" should be treated no differently from any other branch Andy Parkins
2006-12-14 15:29 ` Johannes Schindelin
2006-12-14 15:47   ` Han-Wen Nienhuys
2006-12-14 15:57     ` Johannes Schindelin
2006-12-14 15:59     ` Han-Wen Nienhuys
2006-12-14 16:14       ` Johannes Schindelin
2006-12-15 10:29         ` Jakub Narebski
2006-12-14 18:22     ` Nicolas Pitre
2006-12-14 16:20   ` Jerome Lovy
2006-12-15 21:55     ` Junio C Hamano
2006-12-14 16:25   ` Andy Parkins [this message]
2006-12-14 16:34     ` Andy Parkins
2006-12-14 16:39     ` Johannes Schindelin
2006-12-14 17:42 ` John W. Linville
2006-12-14 18:35   ` Robin Rosenberg
2006-12-14 20:41 ` Junio C Hamano
2006-12-14 21:23   ` Andy Parkins
2006-12-14 21:30     ` Junio C Hamano
2006-12-14 21:37       ` Andy Parkins
2006-12-14 21:57         ` Shawn Pearce
2006-12-15 10:35           ` Jakub Narebski

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=200612141625.08485.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=git@vger.kernel.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 NNTP newsgroup(s).