From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 00/28] clean-ups of static functions and returns
Date: Mon, 14 Aug 2006 23:22:36 +0200 [thread overview]
Message-ID: <ebqphe$1ga$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.63.0608142257130.28360@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin wrote:
> On Mon, 14 Aug 2006, David Rientjes wrote:
>
>> On Mon, 14 Aug 2006, Jakub Narebski wrote:
>> > Could you please make description of patch series email to be parent
>> > (ancestor) of all patches emails, i.e. for patches either to be
>> > chain-replied to introduction email, or all be replies to introduction
>> > email.
>> >
>> > It makes for easier reading/viewing/applying/ignoring the series.
>> >
>>
>> Sure, but you might also want to include this request explicitly in
>> Documentation/SubmittingPatches.
>
> Well... there are people (like yours truly), who still hack there mails in
> pine, and who do not use git-send-email (I had too many problems with
> Perl, and git-send-email _is_ in Perl)... For me, it would be an undue
> burden.
I also not always use git-send-email (because of the box connection to the
net); mu latest series of patches was send using KMail; still it is not
that hard to send patches as reply to introductory letter, or
chain-replied; just reply-all (without quoting) from your "sent" folder.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-08-14 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 20:17 [PATCH 00/28] clean-ups of static functions and returns David Rientjes
2006-08-14 20:33 ` Jakub Narebski
2006-08-14 20:47 ` David Rientjes
2006-08-14 20:59 ` Johannes Schindelin
2006-08-14 21:22 ` Jakub Narebski [this message]
2006-08-14 23:05 ` Junio C Hamano
2006-08-14 23:30 ` David Rientjes
2006-08-15 1:04 ` Junio C Hamano
2006-08-15 1:40 ` trajce nedev
2006-08-15 1:54 ` 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='ebqphe$1ga$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.