From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Rongqing Li <rongqing.li@windriver.com>,
Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] remove the subversion_1.6.15.bb
Date: Mon, 27 Apr 2015 15:12:25 +0100 [thread overview]
Message-ID: <1430143945.13022.120.camel@linuxfoundation.org> (raw)
In-Reply-To: <553DF0CC.4040705@windriver.com>
On Mon, 2015-04-27 at 16:18 +0800, Rongqing Li wrote:
> Hi:
>
> there are two version subversion in oe-core, Do we have special
> need on subversion 1.6.15, if not, I like to remove it
>
> ./meta/recipes-devtools/subversion/subversion_1.8.13.bb
> ./meta/recipes-devtools/subversion/subversion_1.6.15.bb
They changed the on disk format between 1.6 and 1.7 which is why we kept
1.6.x. At this point I personally think it could be removed now though.
CC'ing Martin since I seem to remember he had some interest in this.
Cheers,
Richard
next prev parent reply other threads:[~2015-04-27 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 8:18 [RFC] remove the subversion_1.6.15.bb Rongqing Li
2015-04-27 14:12 ` Richard Purdie [this message]
2015-04-27 14:58 ` 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=1430143945.13022.120.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rongqing.li@windriver.com \
/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