From: "John W. Linville" <linville@tuxdriver.com>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] "master" should be treated no differently from any other branch
Date: Thu, 14 Dec 2006 12:42:57 -0500 [thread overview]
Message-ID: <20061214174251.GA16819@tuxdriver.com> (raw)
In-Reply-To: <200612141519.44294.andyparkins@gmail.com>
On Thu, Dec 14, 2006 at 03:19:44PM +0000, Andy Parkins wrote:
> This patch makes all merge log messages of the form:
>
> Merge branch XXXX into YYYY
>
> Regardless of whether YYYY is master or not.
>
> "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?
Why not drop the "into YYYY" part for everyone else? I don't find
it useful at all, and is just confusing if I merge to a temporary
branch and then pull that into master later.
John
--
John W. Linville
next prev parent reply other threads:[~2006-12-14 18:11 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
2006-12-14 16:34 ` Andy Parkins
2006-12-14 16:39 ` Johannes Schindelin
2006-12-14 17:42 ` John W. Linville [this message]
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=20061214174251.GA16819@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=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 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.