From: Darren Hart <dvhart@linux.intel.com>
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>, poky@yoctoproject.org
Subject: Re: [PATCH 0/3] git-pull: new pull request generation and sending scripts
Date: Sun, 07 Nov 2010 10:18:48 -0500 [thread overview]
Message-ID: <4CD6C358.8010907@linux.intel.com> (raw)
In-Reply-To: <cover.1289057313.git.dvhart@linux.intel.com>
On 11/06/2010 11:28 AM, Darren Hart wrote:
> The following patches replace the existing create-pull-request script and create
> a new send-pull-request. See 2/3 for details on the motivation and functionality
> of the new create-pull-request script.
Thinking about this, I realized that the script would be usefull for
just sending patches as well (for developers without a contrib branch).
Perhaps the scripts should not contain "pull" in their name and the
remote git branch as well as the hosting site should be both optional
and configurable. These are relatively trivial changes which we could
address in a subsequent series if people agree that this initial set is
the right approach for our project.
--
Darren Hart
Embedded Linux Kernel
next prev parent reply other threads:[~2010-11-07 15:18 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 ` Darren Hart [this message]
[not found] ` <4CD782A9.8080201@windriver.com>
2010-11-08 15:59 ` [PATCH 0/3] git-pull: new pull request generation and sending scripts Darren Hart
2010-11-09 0:33 ` Saul Wold
2010-11-09 6:45 ` Darren Hart
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=4CD6C358.8010907@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.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.