From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH] Add script for patch submission via e-mail.
Date: Tue, 05 Jul 2005 08:20:13 -0700 [thread overview]
Message-ID: <7vekadfff6.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050705093441.GD6191@pasky.ji.cz> (Petr Baudis's message of "Tue, 5 Jul 2005 11:34:41 +0200")
>>>>> "PB" == Petr Baudis <pasky@suse.cz> writes:
PB> Any reason why this was not applied? It appears kind of cool.
FYI, the one in <7vll4s47p3.fsf_-_@assigned-by-dhcp.cox.net> is
newer than what you quoted.
One thing _I_ am unhappy about what it does is that it does not
try to be intelligent about merges (I haven't tried the script
on a merged head myself).
When you think about "project lead" vs "individual developer"
modes of operation, the latter is primarily "keep rebasing
commits in my fork and re-throwing them upstream until some of
them stick", so not supporting merges specially would not be so
big a flaw. However, at least it should use --merge-order to
get the epochs decomposed right, in order to produce anything
remotely useful when dealing with a merged head.
next prev parent reply other threads:[~2005-07-05 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 1:32 [PATCH] Add script for patch submission via e-mail Junio C Hamano
2005-07-05 9:34 ` Petr Baudis
2005-07-05 9:39 ` Jon Seymour
2005-07-05 15:20 ` Junio C Hamano [this message]
2005-07-05 16:18 ` Jon Seymour
2005-07-05 20:19 ` Junio C Hamano
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=7vekadfff6.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=torvalds@osdl.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).