git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: hanwen@xs4all.nl
Cc: git@vger.kernel.org
Subject: Re: [PATCH] "master" should be treated no differently from any other branch
Date: Thu, 14 Dec 2006 16:59:05 +0100	[thread overview]
Message-ID: <458174C9.2050401@xs4all.nl> (raw)
In-Reply-To: <4581721B.4050102@xs4all.nl>

Han-Wen Nienhuys escreveu:
> Johannes Schindelin escreveu:
>> Hi,
>>
>> On Thu, 14 Dec 2006, Andy Parkins wrote:
>>
>>> "master" shouldn't get special treatment; making different log messages 
>>> based on the name of the branch is bad form.  What if a user likes 
>>> "my/master" or "my/head" as their master branch?
>> 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 
>> 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?
> 
> Disagree: I have two principal branches, master and stable/2.10.  I don't see
> why the latter should get different commit messages.

Note that this also confused my codeveloper (who is rather enamoured bzr), who
was wondering what the other branch was in case of 

  Merge branch 'master' of ssh+git://git.sv.gnu.org/srv/git/lilypond


Wouldn't it be better to mention the id of the local repository too? 

  Merge branch 'master' of ssh+git://git.sv.gnu.org/srv/git/lilypond into 
  'master' of 'hanwen@xs4all.nl'

this would give more information when these commit messages get pushed to 
someone else.

-- 

  parent reply	other threads:[~2006-12-14 15:59 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 [this message]
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
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=458174C9.2050401@xs4all.nl \
    --to=hanwen@xs4all.nl \
    --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).