From: Andreas Ericsson <ae@op5.se>
To: Nikolai Weibull <mailing-lists.git@rawuncut.elitemail.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-send-mail in sh
Date: Fri, 25 Nov 2005 11:59:07 +0100 [thread overview]
Message-ID: <4386EE7B.7070604@op5.se> (raw)
In-Reply-To: <20051125101209.GA8868@puritan.petwork>
Nikolai Weibull wrote:
>>It's worse than the perl version because;
>>1. It doesn't thread the patch-series (which I personally prefer anyway
>>since it's easier to follow a thread on a particular patch that way).
>
>
> Not so great. Why is it so much more difficult to have one more level
> of nesting? It's annoying, but it's a lot less annoying than having 19
> separate threads that are all, in fact, related to each other.
>
I am of the opinion that nesting is bad because some patches get a few
comments while some others get them in droves. It's easy to miss those
with few if they're all nested. As for finding them, all the threads
should show up next to each other since there's practically no delay
between sending them.
As for implementation, I don't think most "mail" programs have the
functionality necessary to do so (dunno though since I didn't investigate).
>
>>2. The patches sent within the same second arrive in random order.
>
>
> Perhaps adding a 'sleep 1' would help? (The delay may be unacceptable
> to some people, though.)
>
I thought about that, but decided against it.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-11-25 10:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 9:45 git-send-mail in sh Andreas Ericsson
2005-11-25 10:12 ` Nikolai Weibull
2005-11-25 10:59 ` Andreas Ericsson [this message]
2005-11-25 11:06 ` Fernando J. Pereda
2005-11-25 11:05 ` Johannes Schindelin
2005-11-25 14:25 ` Andreas Ericsson
2005-11-25 17:20 ` A Large Angry SCM
2005-11-25 11:15 ` Junio C Hamano
2005-11-25 17:26 ` Andreas Ericsson
2005-11-25 18:30 ` Junio C Hamano
2005-11-26 22:35 ` Andreas Ericsson
2005-11-27 22:01 ` Junio C Hamano
2005-11-27 23:34 ` Andreas Ericsson
2005-11-28 0:15 ` Nikolai Weibull
2005-11-26 20:12 ` Junio C Hamano
2005-11-26 23:34 ` Yann Dirson
2005-11-25 16:33 ` Ryan Anderson
2005-11-25 17:04 ` Andreas Ericsson
2005-11-28 0:49 ` Ryan Anderson
2005-11-28 9:02 ` Andreas Ericsson
2005-11-28 9:34 ` Junio C Hamano
2005-11-29 13:04 ` Andreas Ericsson
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=4386EE7B.7070604@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=mailing-lists.git@rawuncut.elitemail.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).