From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] delete old monotone recipes
Date: Thu, 30 Sep 2010 14:31:24 -0700 [thread overview]
Message-ID: <4CA501AC.2090804@mentor.com> (raw)
In-Reply-To: <AANLkTi=6KMYVWORbcf+BLZYGV6JrscxBEjq-KWXnhzU+@mail.gmail.com>
Frans Meulenbroeks wrote:
> Dear all,
>
> As it stands we have 6 monotone recipes:
>
> monotone-5_0.25.2.bb
> monotone-6_0.27.bb
> monotone-6_0.31.bb
> monotone-6_0.33.bb
> monotone-6_0.34.bb
> monotone-6_0.37.bb
>
> There are all target-only recipes
>
> I can imagine it made sense to have a monotone recipe for the target
> when our sources were still in monotone, but I feel that nowadays it
> is less useful
> (apart from the question whether it is useful to have an SCM on an
> embedded system).
>
> Therefore I would like to bring up the following discussion topics:
>
> Is there any use to keep the old monotone-6 recipes? (all but 0.37).
> Or should we remove?
>
> And what about the monotone-5 recipe. Is that still useful?
>
> And what about the latest monotone-6 recipe? Is that still useful to keep?
>
> Your opinion is appreciated.
As an aside, I can't find anything called monotone-5 or monotone-6, just
monotone. But I'd otherwise suggest the normal rules apply, delete the
unpinned versions assuming they're all GPLv2.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-09-30 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 20:30 [RFC] delete old monotone recipes Frans Meulenbroeks
2010-09-30 21:31 ` Tom Rini [this message]
2010-10-01 5:46 ` Frans Meulenbroeks
2010-10-02 6:51 ` Frans Meulenbroeks
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=4CA501AC.2090804@mentor.com \
--to=tom_rini@mentor.com \
--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.