All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <darren.hart@intel.com>
Cc: yocto@yoctoproject.org, Saul Wold <saul.wold@intel.com>
Subject: Re: Details on Bug #963 kernel tarball corruption.
Date: Fri, 08 Jul 2011 01:08:29 +0100	[thread overview]
Message-ID: <1310083709.20015.863.camel@rex> (raw)
In-Reply-To: <4E164802.4000206@intel.com>

On Thu, 2011-07-07 at 16:57 -0700, Darren Hart wrote:
> On 07/07/2011 02:16 PM, Richard Purdie wrote:
> > On Thu, 2011-07-07 at 13:34 -0700, Flanagan, Elizabeth wrote:
> > diff --git a/bitbake/lib/bb/fetch2/git.py b/bitbake/lib/bb/fetch2/git.py
> > index f3bc793..7954f66 100644
> > --- a/bitbake/lib/bb/fetch2/git.py
> > +++ b/bitbake/lib/bb/fetch2/git.py
> > @@ -170,7 +170,7 @@ class Git(FetchMethod):
> >  
> >          # If the repo still doesn't exist, fallback to cloning it
> >          if not os.path.exists(ud.clonedir):
> > -            clone_cmd = "%s clone --bare %s://%s%s%s %s" % \
> > +            clone_cmd = "%s clone --bare --mirror %s://%s%s%s %s" % \
> 
> 
> --mirror implies --bare, so:
> -            clone_cmd = "%s clone --bare %s://%s%s%s %s" % \
> +            clone_cmd = "%s clone --mirror %s://%s%s%s %s" % \
> 
> should be adequate.

Right, I left it in as it makes it clearer to anyone looking at the
command that we're really sure we want a bare clone...

Cheers,

Richard



  reply	other threads:[~2011-07-08  0:09 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 [this message]
2011-07-07 21:51 ` Tom Zanussi
2011-07-07 22:31   ` Flanagan, Elizabeth
2011-07-07 22:46     ` 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=1310083709.20015.863.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=darren.hart@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.