From: Darren Hart <dvhart@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/1] git fetcher: add support for rebaseable git repo
Date: Fri, 20 May 2011 17:07:57 -0700 [thread overview]
Message-ID: <4DD7025D.10609@linux.intel.com> (raw)
In-Reply-To: <4DD6973B.4020708@gmail.com>
On 05/20/2011 09:30 AM, Khem Raj wrote:
> On 5/15/2011 6:16 PM, Yu Ke wrote:
>> From: Yu Ke<ke.yu@intel.com>
>>
>> Some upstream git repo may rebase in the future, which means current
>> revision may disappear from the upstream repo after the rebase.
>>
>> current git fetcher can not handle this case, because the git mirror
>> tar ball is per repo, and may also change in the rebase and lost the
>> current revision info.
>>
>> To fix this issue, this patch
>> - add rebaseable tag in the SRC_URI
>> - for rebaseable repo, make git mirror tar ball per revision, in this
>> case, even upstream rebase, the git mirror still has the current
>> revision info.
>> - for rebaseable repo, generate mirror tar ball by default, since the
>> repo may change in the future.
>
> Do we have the options to SRC_URI documented somewhere ?
> if yes then this should be added there too.
I was looking and didn't find them. At the very least these should be
documented in the fetch2/git.py file for reference when
reviewing/maintaining the source.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-05-21 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 1:16 [PATCH 0/1] [RFC]git fetch support for rebaseable repo (a.k.a crazy git fetcher) Yu Ke
2011-05-16 1:16 ` [PATCH 1/1] git fetcher: add support for rebaseable git repo Yu Ke
2011-05-20 16:30 ` Khem Raj
2011-05-21 0:07 ` Darren Hart [this message]
2011-05-24 5:50 ` Yu Ke
2011-05-24 14:37 ` Darren Hart
2011-05-17 14:20 ` [PATCH 0/1] [RFC]git fetch support for rebaseable repo (a.k.a crazy git fetcher) Richard Purdie
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=4DD7025D.10609@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.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 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.