git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: Ryan Anderson <ryan@michonline.com>
Cc: junkio@cox.net, git@vger.kernel.org
Subject: Re: [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script
Date: Sun, 31 Jul 2005 14:50:55 +0400	[thread overview]
Message-ID: <20050731145055.2b5e6161.vsu@altlinux.ru> (raw)
In-Reply-To: <11227978451100@foobar.com>

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

On Sun, 31 Jul 2005 04:17:25 -0400 Ryan Anderson wrote:

> This is based off of GregKH's script, send-lots-of-email.pl, and
> strives to do all the nice things a good subsystem maintainer does
> when forwarding a patch or 50 upstream:
> 
> 	All the prior handlers of the patch, as determined by the
> 	Signed-off-by: lines, and/or the author of the commit, are cc:ed
> 	on the email.

> 	All emails are sent as a reply to the previous email, making it
> 	easy to skip a collection of emails that are uninteresting.

Actually, this is the part of GregKH's script which I hate ;)

50 patches sent this way produce an enormous email thread; if someone
then tries to comment on a 40th patch, this part of the thread ends up
far behind the right edge of the message list window in almost any mail
client (and if someone comments on the first patch, the comments are far
from that patch).

Sending a [PATCH 0/N] message with the overall description of the
patchset and then all patches as replies to that message looks much
better in that respect.  However, missing messages in this form are less
obvious.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-07-31 10:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31  8:17 [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-07-31  8:17 ` [PATCH 2/3] Add documentation for git-send-email-script Ryan Anderson
2005-07-31  8:17   ` [PATCH 3/3] Add new dependencies caused by git-send-email-script to debian/control Ryan Anderson
2005-07-31  8:24 ` [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-07-31  9:36   ` Matthias Urlichs
2005-07-31  9:45 ` Junio C Hamano
2005-07-31 19:13   ` Junio C Hamano
2005-07-31 23:52   ` Ryan Anderson
2005-08-01  0:40     ` Junio C Hamano
2005-08-01  7:59       ` Matthias Urlichs
     [not found]     ` <20050801220800.GA12331@uglybox.localnet>
     [not found]       ` <20050801224308.GB12331@uglybox.localnet>
     [not found]         ` <7vk6j52qhn.fsf_-_@assigned-by-dhcp.cox.net>
2005-08-02 12:48           ` [OT] Perl-ish perl vs. C-ish perl Noel Maddy
2005-08-02 16:37             ` Junio C Hamano
2005-08-02 17:20               ` Noel Maddy
2005-08-03  1:30   ` [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-08-03  7:32     ` Matthias Urlichs
2005-07-31 10:25 ` Johannes Schindelin
2005-07-31 23:54   ` Ryan Anderson
2005-07-31 10:50 ` Sergey Vlasov [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=20050731145055.2b5e6161.vsu@altlinux.ru \
    --to=vsu@altlinux.ru \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=ryan@michonline.com \
    /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).