From: Junio C Hamano <junkio@cox.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: git@vger.kernel.org
Subject: Re: Why do we need [PATCH]?
Date: Fri, 16 Dec 2005 13:27:33 -0800 [thread overview]
Message-ID: <7vpsnwenqy.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051216210145.GA25311@mars.ravnborg.org> (Sam Ravnborg's message of "Fri, 16 Dec 2005 22:01:45 +0100")
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? 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.
next prev parent reply other threads:[~2005-12-16 21:28 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 [this message]
2005-12-16 21:42 ` Sam Ravnborg
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=7vpsnwenqy.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=sam@ravnborg.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).