From: Caspar Zhang <caspar@casparzhang.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH/RFC] style-guide: sending patch series
Date: Mon, 09 Jul 2012 18:17:18 +0800 [thread overview]
Message-ID: <4FFAAFAE.4080607@casparzhang.com> (raw)
In-Reply-To: <49d6e6bd-1813-435d-aa6c-aaa8459b9979@zmail17.collab.prod.int.phx2.redhat.com>
On 07/09/2012 03:00 PM, Jan Stancek wrote:
>
>
> ----- Original Message -----
>> From: "Caspar Zhang" <caspar@casparzhang.com>
>> To: "Jan Stancek" <jstancek@redhat.com>
>> Cc: ltp-list@lists.sourceforge.net
>> Sent: Friday, 29 June, 2012 10:53:55 AM
>> Subject: Re: [LTP] [PATCH/RFC] style-guide: sending patch series
>>
>> On 06/29/2012 04:44 PM, Jan Stancek wrote:
>>> +git config format.numbered auto
>>> +git config sendemail.signoffbycc false
>>> +git config sendemail.suppresscc all
>>> +git config sendemail.suppressfrom true
>>> +git config sendemail.smtpserver "your.smtp.server"
>>> +git config sendemail.confirm always
>>
>> These lines look like not related to thread-shallow issue?
>
> (sorry for late answer, was on holiday)
>
> True, those are related to sending patch series with git send-email in general.
> I took 'best practices' from different mailing list as initial suggestion.
Okay. This caused a little confusion to me, I thought you were
suggesting use all configurations above as "shallow thread" style.
BTW, I don't think they[1] are necessary to put in style-guide.txt,
they're more likely to be tips instead. i.e. we don't _require_ patch
contributor to avoid cc-ing to people in sign-off-by lines, nor require
they to suppress cc/from, blah, blah, etc.
Also, on my system, this line is not required either:
+git config sendemail.thread false
once you have set this:
+git config format.thread shallow
Whenever I enable or disable thread in sendemail section, the patchset
will be displayed as shallow format.
Thanks,
Caspar
[1] "they" refers to:
>>> +git config sendemail.signoffbycc false
>>> +git config sendemail.suppresscc all
>>> +git config sendemail.suppressfrom true
>>> +git config sendemail.smtpserver "your.smtp.server"
>>> +git config sendemail.confirm always
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-07-09 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 8:44 [LTP] [PATCH/RFC] style-guide: sending patch series Jan Stancek
2012-06-29 8:53 ` Caspar Zhang
2012-06-29 9:03 ` [LTP] getrusage04 FAIL : stime increased > 2000us Nitin Yadav
2012-07-09 7:00 ` [LTP] [PATCH/RFC] style-guide: sending patch series Jan Stancek
2012-07-09 10:17 ` Caspar Zhang [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=4FFAAFAE.4080607@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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