From: Jari Aalto <jari.aalto@cante.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] Checklist clarifications: added "Commits", "Patch:" headings
Date: Mon, 30 Apr 2007 15:02:50 +0300 [thread overview]
Message-ID: <abwqxe6t.fsf@cante.net> (raw)
In-Reply-To: Pine.LNX.4.64.0704301333400.29859@racer.site
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi,
>
> On Mon, 30 Apr 2007, Jari Aalto wrote:
>
>> + - send your patch to <git@vger.kernel.org> by using
>> + git-format-patch(1) with option "-M". See also
>> + git-send-email(1).
>> - do not PGP sign your patch
>> - - use "git format-patch -M" to create the patch
>
> NACK.
>
> I never use send-email myself. There are even technical issues to my
> excuse: sometimes I cannot send the mails from my machine. So, this should
> not be a _replacement_ for `git format-patch -M && send mail manually`,
> but only an _alternative_.
>
> However, my impression was that many people had problems when first
> sending patches with send-email. There should be _at least_ a word of
> caution, that you should test the operation on something different than
> the Git list first.
Is this workding okay?
- send your patch to <git@vger.kernel.org> by using
git-format-patch(1) with option "-M". If you use
git-send-email(1), please test it first by sending
email to yourself.
Jari
next prev parent reply other threads:[~2007-04-30 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 11:04 [PATCH] Checklist clarifications: added "Commits", "Patch:" headings Jari Aalto
2007-04-30 11:36 ` Johannes Schindelin
2007-04-30 12:02 ` Jari Aalto [this message]
2007-04-30 12:09 ` Julian Phillips
2007-04-30 12:42 ` Johannes Schindelin
2007-04-30 16:04 ` [PATCH] v2: " Jari Aalto
2007-04-30 23:35 ` Junio C Hamano
2007-04-30 21:00 ` [PATCH] send-email: add a few config variables Junio C Hamano
2007-05-01 4:11 ` [PATCH] Checklist clarifications: added "Commits", "Patch:" headings 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=abwqxe6t.fsf@cante.net \
--to=jari.aalto@cante.net \
--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.