From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] git: do not execute 'git remote prune'
Date: Wed, 04 Jul 2012 14:43:17 +0100 [thread overview]
Message-ID: <1341409397.3906.25.camel@ted> (raw)
In-Reply-To: <1341084896-29686-1-git-send-email-enrico.scholz@sigma-chemnitz.de>
On Sat, 2012-06-30 at 21:34 +0200, Enrico Scholz wrote:
> 'git remote prune' at this location does not make much sense because
> the following 'git remote rm' will prune stale and non-stale branches.
>
> The 'prune' can cause trouble because it will access the network
> bypassing the no-network code in bitbake. When this operation fails and
> throws an exception, the next command (--> 'git remote rm') will be
> skipped. This in turn, will make all the following operations fail,
> because they assume that the remote does not exist yet.
>
> Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
> ---
> lib/bb/fetch2/git.py | 1 -
> 1 file changed, 1 deletion(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-07-04 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 19:34 [PATCH] git: do not execute 'git remote prune' Enrico Scholz
2012-07-04 13:43 ` 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=1341409397.3906.25.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=enrico.scholz@sigma-chemnitz.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox