From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: RFC One recipe with two git repository as sources
Date: Thu, 23 Jun 2011 09:37:28 -0500 [thread overview]
Message-ID: <4E034FA8.60902@windriver.com> (raw)
In-Reply-To: <1308839149.21613.165.camel@phil-desktop>
On 6/23/11 9:25 AM, Phil Blundell wrote:
> On Thu, 2011-06-23 at 13:36 +0200, Holger Freyther wrote:
>> On 06/23/2011 01:21 PM, Phil Blundell wrote:
>>> On Thu, 2011-06-23 at 13:18 +0200, Holger Freyther wrote:
>>>> - destdir = os.path.join(destdir, "git/")
>>>> + destsuffix = ud.parm.get("destsuffix", "git/")
>>>> + print destsuffix
>>>> + destdir = os.path.join(destdir, destsuffix)
>>>
>>> I think that "print" might be extraneous, but other than this your patch
>>> looks awesome. I think this would resolve the problem that I was having
>>> in.
>>
>> great, yeah the print is bogus and the question if and how this applies to
>> fetch/git.py is also unresolved (i had a quick look but have not found the
>> dirname it uses to create the tarball).
>
> I'm not entirely clear on what's going on with fetch vs fetch2 at all,
> in terms of whether fetch is going away at some point or the two of them
> are meant to be existing in parallel. Can one of the TSC überhackers
> shed any light on what the intent is there?
>
"fetch" is remaining for compatibility for the time being. I believe the intent
is that fetch will go away when compatibility is no longer needed or desired.
--Mark
> p.
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2011-06-23 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 11:18 RFC One recipe with two git repository as sources Holger Freyther
2011-06-23 11:21 ` Phil Blundell
2011-06-23 11:36 ` Holger Freyther
2011-06-23 14:25 ` Phil Blundell
2011-06-23 14:37 ` Mark Hatle [this message]
2011-06-23 14:37 ` Koen Kooi
2011-07-01 13:37 ` [oe] " Holger Freyther
2011-07-01 13:37 ` Holger Freyther
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=4E034FA8.60902@windriver.com \
--to=mark.hatle@windriver.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.