git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Why do we need [PATCH]?
Date: Fri, 16 Dec 2005 22:42:31 +0100	[thread overview]
Message-ID: <20051216214231.GA2903@mars.ravnborg.org> (raw)
In-Reply-To: <7vpsnwenqy.fsf@assigned-by-dhcp.cox.net>

On Fri, Dec 16, 2005 at 01:27:33PM -0800, Junio C Hamano wrote:
> Sam Ravnborg <sam@ravnborg.org> writes:
> 
> > I looked at the source and found the -k option, but adding [PATCH]
> > should not be default behaviour so this is not the correct solution.
> 
> The "correct" solution depends on where you come from.  That
> extra [PATCH] is a carryover from BK days, I was told by Linus,
> to make e-mailed things stand out --- I've never used BK but I
> am guessing that things were not as obvious as our commit
> messages, perhaps?
You can a typical bk commit here:
http://linus.bkbits.net:8080/linux-2.5/cset@1.2243?nav=index.html|ChangeSet@-9M

And here it made much more sense sine the author/comitter info are
less structured. Also we do nto have the Signed-off-by: stuff back then.

> We have "Author/Committer" distinction so
> the [PATCH] marker is redundant.
> 
> The rewrite, "git-am" does not bother with adding [PATCH], but
> the original "git-applymbox", being everyday Linus' tool, was
> left as it was, not to disrupt the workflow of Linus.

Thanks, I had forgotten the git-am rewrite.
I will use that in the future - if I remember.

	Sam

      reply	other threads:[~2005-12-16 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-16 21:01 Why do we need [PATCH]? Sam Ravnborg
2005-12-16 21:13 ` Dave Jones
2005-12-16 21:14 ` Brian Gerst
2005-12-16 21:27 ` Junio C Hamano
2005-12-16 21:42   ` Sam Ravnborg [this message]

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=20051216214231.GA2903@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).