From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 0/3] RFC: Integrating gitpkgv functionality
Date: Sat, 23 May 2015 08:16:24 +0100 [thread overview]
Message-ID: <1432365384.12832.53.camel@linuxfoundation.org> (raw)
In-Reply-To: <1432276145-31264-1-git-send-email-mike.looijmans@topic.nl>
On Fri, 2015-05-22 at 08:29 +0200, Mike Looijmans wrote:
> Follow-up on the discussion here:
> http://lists.openembedded.org/pipermail/openembedded-core/2015-January/100345.html
>
> This is an implementation of gitpkgv in OE-core. It modifies the fetcher
> to optionally provide an incremental numbering scheme for GIT repositories.
>
> These three patches implement this, and provide the functionality in three stages.
> 1 __init__.py: Allows fetchers to provide alternatives to formatting a version string.
> 2 git.py: Implements such alternative formatting in gitpkgv style.
> 3 bitbake.conf: Sets GITPKGV so that it becomes backwards compatible with gitpkgv.
>
> v2: Rebased and added bitbake.conf patch to set GITPKGV
>
> Mike Looijmans (3):
> fetch2/__init__.py: Make get_srcrev output configurable
> fetch2/git.py: Add gitpkgv_revision alternative version information
> bitbake.conf: Set GITPKGV variable
FWIW this looks quite neat to me, thanks!
Cheers,
Richard
prev parent reply other threads:[~2015-05-23 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 6:29 [PATCH v2 0/3] RFC: Integrating gitpkgv functionality Mike Looijmans
2015-05-22 6:29 ` [PATCH v2 1/3] fetch2/__init__.py: Make get_srcrev output configurable Mike Looijmans
2015-05-22 6:29 ` [PATCH v2 2/3] fetch2/git.py: Add gitpkgv_revision alternative version information Mike Looijmans
2015-05-22 6:29 ` [PATCH v2 3/3] bitbake.conf: Set GITPKGV variable Mike Looijmans
2015-06-09 8:50 ` Mike Looijmans
2015-06-09 9:56 ` Paul Eggleton
2015-06-09 10:13 ` Richard Purdie
2015-05-23 7:16 ` Richard Purdie [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=1432365384.12832.53.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mike.looijmans@topic.nl \
--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