From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: [stable] floating revisions or _svn/_git/_cvs recipes
Date: Tue, 31 Mar 2009 22:13:06 +0200 [thread overview]
Message-ID: <49D27952.6060806@gmx.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
Hi,
the new stable branch has been created. Soon we will see an influx of
$BIG_COMPANY making use it. ;)
All great. :)
However I see a problem with those recipes which do not have a fixed
version. I mean those that have _svn, _git or _cvs as the version number
and are configured to autorev.
Can we come to an agreement and say: "Only limited support for those
recipes."
Attached to this topic is the wish to introduce a server containing the
source tarballs for the recipes we provide.
I think everybody knows the trouble that we have with various tarballs
which we take right from the Debian repos. As soon as a new tarball is
uploaded the old one vanishes. I think this will cause grief for our
stable branch and I would like to avoid this.
Regards
Robert
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]
next reply other threads:[~2009-03-31 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 20:13 Robert Schuster [this message]
2009-03-31 20:15 ` [stable] floating revisions or _svn/_git/_cvs recipes Koen Kooi
2009-03-31 20:26 ` Tom Rini
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=49D27952.6060806@gmx.net \
--to=thebohemian@gmx.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.