All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][PATCH v2] plowshare: Add Git version (initial recipe)
Date: Wed, 15 Aug 2012 10:53:42 +0200	[thread overview]
Message-ID: <k0fo2k$fqc$1@dough.gmane.org> (raw)
In-Reply-To: <502B613B.4020200@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 15-08-12 10:43, Matthieu Crapet schreef:
> Hi,
> 
> Thanks for answer! The path in the "diff --git" line is not good. 
> "meta-openembedded-contrib/meta-oe/recipes-support" is my suggestion. 
> However, I don't know if this kind of software is suitable for oe-devel.
> I just wanted to create a "valid" recipe.
> 
> I'm still confused with this SRCREV thing. Just want to retrieve HEAD
> from git master branch.

That's not allowed, all SRCREVs must be locked down. If there's an update
you want/need, send a patch. Most people stop looking after AUTOREV recipes
after a month or so and everyone else gets to live with the breakage.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFQK2OWMkyGM64RGpERAlWtAKCMwXpuClb8p1obLjU7PVMlni1d6gCcDsDI
CWuOwmaAtY+bHTFZO/F/g/s=
=eBzs
-----END PGP SIGNATURE-----




  reply	other threads:[~2012-08-15  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14  9:48 [RFC][PATCH] plowshare: Add Git version (initial recipe) Matthieu
2012-08-14  9:57 ` Koen Kooi
2012-08-14 12:50   ` [RFC][PATCH v2] " Matthieu
2012-08-14 17:40     ` Jack Mitchell
2012-08-15  8:43       ` Matthieu Crapet
2012-08-15  8:53         ` Koen Kooi [this message]
2012-08-15  9:27           ` Paul Eggleton

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='k0fo2k$fqc$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@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.