From: Mike Looijmans <mike.looijmans@topic.nl>
To: OE <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] RFC: Integrating gitpkgv functionality
Date: Sun, 08 Mar 2015 13:29:19 +0100 [thread overview]
Message-ID: <54FC409F.9040107@topic.nl> (raw)
In-Reply-To: <1422713174-18522-1-git-send-email-mike.looijmans@topic.nl>
On 31-01-15 15:06, Mike Looijmans wrote:
> Follow-up on the discussion here:
> http://lists.openembedded.org/pipermail/openembedded-core/2015-January/100345.html
>
> This is a preliminary implementation of gitpkgv in OE-core. It modifies the
> fetcher to optionally provide an incremental numbering scheme for GIT
> repositories.
>
> These two patches implement this. The change in __init__ is basically ready for
> public consumption. The modification to git.py is a prototype that I've used to
> test feasibility. It imitates gitpkgv perfectly for the recipes I tried.
>
> To make this ready for production, we should provide better names and likely
> a GITPKGV or similarly named variable that can be used in recipes instead of
> "${@bb.fetch2.get_srcrev(d, 'gitpkgv_revision')}".
>
> Mike Looijmans (2):
> fetch2/__init__.py: Make get_srcrev output configurable
> fetch2/git.py: Add gitpkgv_revision alternative version information
>
> lib/bb/fetch2/__init__.py | 9 ++++++---
> lib/bb/fetch2/git.py | 25 +++++++++++++++++++++++++
> 2 files changed, 31 insertions(+), 3 deletions(-)
>
--
Mike Looijmans
prev parent reply other threads:[~2015-03-08 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 14:06 [PATCH 0/2] RFC: Integrating gitpkgv functionality Mike Looijmans
2015-01-31 14:06 ` [PATCH 1/2] fetch2/__init__.py: Make get_srcrev output configurable Mike Looijmans
2015-02-02 20:50 ` Otavio Salvador
2015-02-03 6:17 ` Mike Looijmans
2015-02-03 11:00 ` Otavio Salvador
2015-01-31 14:06 ` [PATCH 2/2] fetch2/git.py: Add gitpkgv_revision alternative version information Mike Looijmans
2015-03-08 12:29 ` Mike Looijmans [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=54FC409F.9040107@topic.nl \
--to=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