From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] createrepo: Implement --dbpath command line option
Date: Wed, 1 Apr 2015 14:19:36 +0300 [thread overview]
Message-ID: <20150401111936.GA10151@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYLsPht9UmqOZgHcFwMFftfFi6rRkFyFztHyGChGdwubA@mail.gmail.com>
On Tue, Mar 31, 2015 at 10:25:11PM +0100, Burton, Ross wrote:
> Hi Ed,
>
> On 31 March 2015 at 00:49, Ed Bartosh <ed.bartosh@linux.intel.com> wrote:
>
> > Upstream-Status: Pending
> >
>
> The commit log needs just a Signed-off-by; the patch needs an explanation,
> Signed-off-by, and Upstream-Status. The goal is that the patch itself is
> self-explanatory, so should explain what it does and why, whether it went
> upstream and why (not), and who admits creating it in the first place.
>
Thanks for the explanations. I'll update the patch.
Regards,
Ed
next prev parent reply other threads:[~2015-04-01 11:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 8:30 [PATCH] rootfs.py: Remove rpm database from staging area Ed Bartosh
2015-03-30 8:53 ` Richard Purdie
2015-03-30 14:56 ` Mark Hatle
2015-03-30 15:14 ` Mark Hatle
2015-03-30 19:00 ` Ed Bartosh
2015-03-30 19:22 ` Mark Hatle
2015-03-30 22:47 ` Ed Bartosh
2015-03-30 23:49 ` [PATCH] createrepo: Implement --dbpath command line option Ed Bartosh
2015-03-31 0:16 ` [PATCH] package_manager: call createrepo with --dbpath pointing inside WORKDIR Ed Bartosh
2015-03-31 12:06 ` Richard Purdie
2015-03-31 16:09 ` Mark Hatle
2015-04-01 11:17 ` Ed Bartosh
2015-03-31 21:25 ` [PATCH] createrepo: Implement --dbpath command line option Burton, Ross
2015-04-01 11:19 ` Ed Bartosh [this message]
2015-04-01 12:06 ` Ed Bartosh
2015-04-01 12:12 ` Ed Bartosh
-- strict thread matches above, loose matches on Subject: below --
2015-04-01 12:09 Ed Bartosh
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=20150401111936.GA10151@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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.