git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] "master" should be treated no differently from any other branch
Date: Fri, 15 Dec 2006 11:29:01 +0100	[thread overview]
Message-ID: <eltt8n$h4s$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.63.0612141710400.3635@wbgn013.biozentrum.uni-wuerzburg.de

Johannes Schindelin wrote:

> On Thu, 14 Dec 2006, Han-Wen Nienhuys wrote:
> 
>> 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.
> 
> And why not put your address and birthday in there, too?
> 
> Frankly, it does not matter. In my private git repository I see that I 
> often merged from this machine to that machine, criss-crossing often. It 
> does not buy me anything to even know _where_ I got it from.
> 
> Besides, the information you are most likely looking for is the committer, 
> which is recorded anyway.
> 
> The single most useful information in the Merge message is the name of the 
> branch I merged, since it is more often than not a topic branch, which is 
> aptly named.

By the way, I run git with merge.summary=true, and it is very nice and
usually shows the correct thing... but because git doesn't mark branching
points in any way sometimes under feature branch header there are changes
not related to given topic, but which were on given branch; the
fast-forward case I think.

That said, I'm all for not having "master" branch special-cased, besides
having it default name for branch in git-init-db.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git


  reply	other threads:[~2006-12-15 10:26 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 [this message]
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='eltt8n$h4s$1@sea.gmane.org' \
    --to=jnareb@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).