From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: git-native?
Date: Tue, 21 Oct 2008 00:37:42 +0200 [thread overview]
Message-ID: <gdj17m$9pg$1@ger.gmane.org> (raw)
In-Reply-To: <1224536247.4235.282.camel@lenovo.internal.reciva.com>
On 20-10-2008 22:57, Phil Blundell wrote:
> On Mon, 2008-10-20 at 14:32 -0500, Mike (mwester) wrote:
>> Er, just a thought... but now that we've switched to git, should OE just
>> globally ASSUME_PROVIDED for git-native?
>
> I'm not sure what that would really buy you. It would be a pain for
> downstream OE users who might be getting the metadata through some other
> means (rather than checking it out directly from the OE git tree), and
> it doesn't really seem like it would bring any great benefit.
> Individual users can obviously set ASSUME_PROVIDED for git-native if
> they want and I guess they should continue to do that.
IIRC git-native was added for people without git (e.g. RHEL) or people
only having old git versions (e.g. git 1.4) that the fetcher doesn't like.
So removing it would have no positive effect other than shortening
initial build time with a few seconds.
regards,
Koen
prev parent reply other threads:[~2008-10-20 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 19:32 git-native? Mike (mwester)
2008-10-20 20:57 ` git-native? Phil Blundell
2008-10-20 22:37 ` Koen Kooi [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='gdj17m$9pg$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.