From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] create-pull-request: Add -l location switch
Date: Wed, 11 May 2011 18:03:38 +0100 [thread overview]
Message-ID: <1305133418.30391.425.camel@rex> (raw)
In-Reply-To: <4DC9C3B2.3050201@mentor.com>
On Tue, 2011-05-10 at 16:01 -0700, Tom Rini wrote:
> On 05/10/2011 12:18 PM, Otavio Salvador wrote:
> > On Tue, May 10, 2011 at 15:55, Tom Rini <tom_rini@mentor.com> wrote:
> >> Add a -l switch that takes an argument of either github or gitorious
> >> and will make the cover letter have a fill-in-the-blank of where the
> >> changes are on either github or gitorious.
> >
> > Another possibility would be to use git config interface to store
> > those. You might have something like:
> >
> > [oe-core-pull-request]
> > mode = github
> > user = foo
> >
> > or
> >
> > [oe-core-pull-request]
> > mode = gitorious
> > user = bar
> >
> > This could be used to fill the fields in a proper way since those are
> > predictable.
>
> If I had a good bit more time, I might re-write the script in python and
> parse .ini files (same syntax as gitconfig) so that lots of useful
> defaults could be saved. But here's the real test, given that you're an
> intended user, would you use the -l switch or just make a local change
> to the script like Martin showed?
FWIW, we could at least extract a url from the .config of the git
repository with a command like "git remote -v show oe-core-pull-request"
Cheers,
Richard
next prev parent reply other threads:[~2011-05-11 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 18:55 [PATCH] create-pull-request: Add -l location switch Tom Rini
2011-05-10 19:18 ` Otavio Salvador
2011-05-10 23:01 ` Tom Rini
2011-05-11 6:02 ` Martin Jansa
2011-05-11 17:03 ` Richard Purdie [this message]
2011-05-11 18:28 ` Darren Hart
2011-05-12 0:55 ` Otavio Salvador
2011-05-11 5:43 ` 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=1305133418.30391.425.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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