From: Darren Hart <dvhart@linux.intel.com>
To: Saul Wold <saul.wold@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 0/3] git-pull: new pull request generation and sending scripts
Date: Mon, 08 Nov 2010 22:45:48 -0800 [thread overview]
Message-ID: <4CD8EE1C.7060701@linux.intel.com> (raw)
In-Reply-To: <4CD896F7.2000603@intel.com>
On 11/08/2010 04:33 PM, Saul Wold wrote:
> On 11/08/2010 07:59 AM, Darren Hart wrote:
Hey Saul,
Thanks for the review!
> I think we also need a way to only send the initial email (and not the
> patches) since I work with the team to pull together multiple patches
> that are already on the list and re-send the request to the Yocto alias,
> I don't want to flood the list with duplicate match info.
This is really no different that it was originally. Just load the
0000-cover-letter.txt into your favorite MUA and send away.
Alternatively, you can just delete the other messages and use
send-pull-request.sh.
I'd rather not make an option that makes it easy for people to not send
the patches, as it may become the norm (as that is the habit people are
already in). Will one of the options I mentioned work for you?
>
> Also on a minor nit note: can you change the Branch to include contrib/
> that way it can be a cut and paste for doing some of the local git
> operations.
The name "contrib" is user defined and cannot be relied upon to be the
same on every system. The branch is relative to the poky-contrib.git
repository, prepending "contrib" wouldn't be accurate.
>> Excellent - and this brings up a point I wanted to discuss. One of the
>> stated reasons for doing this was to facilitate peer review. Now that I
>> have Bruce's Acked-by:, I could reword the commit messages to include
>> them, or Richard could add them when he does the pull, but I do think
>> they should be present in the final commits to poky proper.
>>
> I am not sure we need to get into updating the patch or commit messages
> with Acked-by lines, the email archives should suffice.
It can be difficult to map commits to email threads, and when the ack
occurs elsewhere, the history is completely lost. We don't need to track
every "I like this patch", but I believe it is good practice to track
key Acks from key reviewers.
Thanks,
--
Darren Hart
Embedded Linux Kernel
prev parent reply other threads:[~2010-11-09 6:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 15:28 [PATCH 0/3] git-pull: new pull request generation and sending scripts Darren Hart
2010-11-06 13:35 ` [PATCH 1/3] git pull: remove the existing create_pull_request script Darren Hart
2010-11-06 13:42 ` [PATCH 2/3] git-pull: add the new create-pull-request script Darren Hart
2010-11-06 14:06 ` [PATCH 3/3] git-pull: add send-pull-request script Darren Hart
2010-11-07 15:18 ` [PATCH 0/3] git-pull: new pull request generation and sending scripts Darren Hart
[not found] ` <4CD782A9.8080201@windriver.com>
2010-11-08 15:59 ` Darren Hart
2010-11-09 0:33 ` Saul Wold
2010-11-09 6:45 ` Darren Hart [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=4CD8EE1C.7060701@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=saul.wold@intel.com \
/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.