From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: SRC_URI and latest HEAD revision with git
Date: Mon, 22 Jul 2013 08:21:16 +0200 [thread overview]
Message-ID: <51ECCF5C.2020505@dresearch-fe.de> (raw)
After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.
Cheers,
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next reply other threads:[~2013-07-22 6:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 6:21 Steffen Sledz [this message]
2013-07-22 9:01 ` SRC_URI and latest HEAD revision with git Nicolas Dechesne
2013-07-22 9:46 ` Steffen Sledz
2013-07-22 9:51 ` Paul Eggleton
2013-07-22 10:30 ` Steffen Sledz
2013-07-22 11:08 ` Paul Eggleton
2013-07-22 12:42 ` Martin Jansa
2013-07-23 6:23 ` Steffen Sledz
2013-07-23 8:20 ` Paul Eggleton
2013-07-31 10:02 ` SRC_URI and latest HEAD revision with git (in oe-classic) Steffen Sledz
2013-07-31 10:02 ` [OE-core] " Steffen Sledz
2013-07-31 12:50 ` [oe] " Paul Eggleton
2013-07-31 12:50 ` [OE-core] " Paul Eggleton
2013-08-01 6:11 ` [oe] " Steffen Sledz
2013-08-01 6:11 ` [OE-core] " Steffen Sledz
2013-08-01 10:36 ` [oe] " Martin Jansa
2013-08-01 10:36 ` [OE-core] " Martin Jansa
2013-08-01 10:52 ` [oe] " Steffen Sledz
2013-08-01 10:52 ` [OE-core] " Steffen Sledz
2013-08-01 11:37 ` [oe] " Martin Jansa
2013-08-01 11:37 ` [OE-core] " Martin Jansa
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=51ECCF5C.2020505@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--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 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.