From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
Cc: "Hart, Darren" <darren.hart@intel.com>,
"Wold, Saul" <saul.wold@intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Details on Bug #963 kernel tarball corruption.
Date: Thu, 07 Jul 2011 23:46:59 +0100 [thread overview]
Message-ID: <1310078819.20015.852.camel@rex> (raw)
In-Reply-To: <CAPhnLPA2qgc1S_Wo0+sVaqDJpN_7RVmrhpEgEwu7mzGRpveqKw@mail.gmail.com>
On Thu, 2011-07-07 at 15:31 -0700, Flanagan, Elizabeth wrote:
> On Thu, Jul 7, 2011 at 2:51 PM, Tom Zanussi <tom.zanussi@intel.com> wrote:
> > On Thu, 2011-07-07 at 13:34 -0700, Flanagan, Elizabeth wrote:
> >
> > Shouldn't this always be the state of DL_DIR i.e. any change made to the
> > contents of SRC_URI be exactly reflected in the same thing in DL_DIR?
> > If that were the case, I think it would solve the problems below as well
> > as the original problem in the bug report where downstream is apparently
> > being served the resulting badness in DL_DIR...
>
> It should and in a clean DL_DIR, do_fetch does, in fact, clone
> correctly. But do_fetch with an already populated fetched repo in
> DL_DIR causes it to get dirty by placing new branches in
> remotes/origin. This is caused by fetch, however, looking at
> do_kernel_checkout, it seems as if this was at one point, expected
> behavior.
It is expected, *but* it should also update the local heads in sync with
the remotes.
The --mirror options claims to do this and should be exactly what is
missing...
Cheers,
Richard
prev parent reply other threads:[~2011-07-07 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 20:34 Details on Bug #963 kernel tarball corruption Flanagan, Elizabeth
2011-07-07 20:42 ` Flanagan, Elizabeth
2011-07-07 21:16 ` Richard Purdie
2011-07-07 23:57 ` Darren Hart
2011-07-08 0:08 ` Richard Purdie
2011-07-07 21:51 ` Tom Zanussi
2011-07-07 22:31 ` Flanagan, Elizabeth
2011-07-07 22:46 ` Richard Purdie [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=1310078819.20015.852.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=darren.hart@intel.com \
--cc=elizabeth.flanagan@intel.com \
--cc=saul.wold@intel.com \
--cc=yocto@yoctoproject.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.