From: Tian <tiansm@lemote.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Kumba <kumba@gentoo.org>, linux-mips@linux-mips.org
Subject: Re: Mailing patches
Date: Wed, 06 Jun 2007 13:09:32 +0800 [thread overview]
Message-ID: <4666418C.9040401@lemote.com> (raw)
In-Reply-To: <20070605152338.GA22937@linux-mips.org>
sorry for the mess,when git-format-patch , wo forgot the -n para
and i would like to know what command para is recommended for sending
patch on maillist?
git-send-email --no-chain-reply-to --compose --from tiansm@lemote.com
--no-signed-off-by-cc --smtp-server <server> --subject "Lemote Loongson
2E patch update" --suppress-from --to linux-mips@linux-mips.org 00*
--no-chain-reply-to or --chain-reply-to ?
and.....should i resend the patches?
Tian
Ralf Baechle wrote:
> On Mon, Jun 04, 2007 at 11:40:02PM -0400, Kumba wrote:
>
>
>> What about just attaching the patches to a message? Seems like it'll avoid
>> most of the problems Tbird has with them. I'm just not sure if that
>> hampers importing them into git or not.
>>
>
> There are issues if people have the log message in the attachment as
> well. And of course there is still the prime reason why attachments
> are a no-no - most mailers won't quote them so commenting on them is
> hard when discussing things.
>
> Git has some limited abilities to handle MIME messages since quite a
> while though. But quilt which is the heart of how I manage the queue
> tree doesn't.
>
> Ralf
>
>
>
>
next prev parent reply other threads:[~2007-06-06 5:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 13:35 Mailing patches Ralf Baechle
2007-06-05 3:40 ` Kumba
2007-06-05 3:54 ` Kumba
2007-06-05 15:24 ` Ralf Baechle
2007-06-05 15:23 ` Ralf Baechle
2007-06-06 5:09 ` Tian [this message]
2007-06-06 6:33 ` Franck Bui-Huu
2007-06-06 7:24 ` Tian
2007-06-06 7:48 ` Franck Bui-Huu
2007-06-06 16:58 ` Ralf Baechle
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=4666418C.9040401@lemote.com \
--to=tiansm@lemote.com \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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