Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster <akuster@mvista.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	 Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] V2 lz4: update to latest version
Date: Wed, 16 Jul 2014 12:07:16 -0700	[thread overview]
Message-ID: <53C6CD64.2090807@mvista.com> (raw)
In-Reply-To: <CAJTo0LY6uP-92RmP31eTNZtb5cPkor1d2Ornw0q-Okd2E0KGYg@mail.gmail.com>


Did not mean to generate extra work for you all.

Thanks for the input. I will go back to the drawing board.

regards,
Armin
On 07/16/2014 06:48 AM, Burton, Ross wrote:
> On 16 July 2014 10:11, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> I'm still a little concerned about this change from svn to git. Which is
>> the definitive source? It looks like the svn repo is active too?
>>
>> I just don't want to end up in a position where we're pulling from
>> someone's hack'n'dev version of lz4 rather than the place considered the
>> real "master" source...
> The revision histories *are* different (commits marked "untested" and
> then fixed in another commit) but the owner of the git repo is the
> same as the owner of the svn repo.  It looks like git is his working
> area and then changes that have been tested are merged and committed
> to git.
>
> Unless there's a good reason I'd keep with the svn repo for now.
>
> Ross



      reply	other threads:[~2014-07-16 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  1:41 [meta-oe][PATCH] V2 lz4: update to latest version Armin Kuster
2014-07-15  5:30 ` akuster
2014-07-16  9:11 ` Richard Purdie
2014-07-16 13:48   ` Burton, Ross
2014-07-16 19:07     ` akuster [this message]

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=53C6CD64.2090807@mvista.com \
    --to=akuster@mvista.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@intel.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