All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Matt Madison <matt@madison.systems>,
	bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v2] fetch2: preserve current working directory
Date: Sat, 20 Aug 2016 16:10:29 +0100	[thread overview]
Message-ID: <1471705829.16712.70.camel@linuxfoundation.org> (raw)
In-Reply-To: <1470848896-23041-2-git-send-email-matt@madison.systems>

On Wed, 2016-08-10 at 10:08 -0700, Matt Madison wrote:
> Fix the methods in all fetchers so they don't change
> the current working directory of the calling process, which
> could lead to "changed cwd" warnings from bitbake.
> 
> Signed-off-by: Matt Madison <matt@madison.systems>
> ---
>  lib/bb/fetch2/__init__.py  | 21 +++++++++++----------
>  lib/bb/fetch2/bzr.py       | 11 ++++-------
>  lib/bb/fetch2/clearcase.py |  6 ++----
>  lib/bb/fetch2/cvs.py       | 15 ++++++++-------
>  lib/bb/fetch2/git.py       | 45 ++++++++++++++++++++----------------
> ---------
>  lib/bb/fetch2/gitannex.py  | 24 +++++++++++-------------
>  lib/bb/fetch2/gitsm.py     | 23 ++++++++++-------------
>  lib/bb/fetch2/hg.py        | 28 ++++++++++------------------
>  lib/bb/fetch2/npm.py       | 22 +++++++---------------
>  lib/bb/fetch2/osc.py       | 10 ++++------
>  lib/bb/fetch2/perforce.py  |  6 ++----
>  lib/bb/fetch2/repo.py      | 13 ++++++-------
>  lib/bb/fetch2/svn.py       | 13 +++++--------
>  13 files changed, 100 insertions(+), 137 deletions(-)

Thanks for this, sorry it took a while to merge. It does looks like a
pretty good cleanup of this code and is much appreciated!

I did wonder if we still needed the try_mirror chdir now we've cleaned
up the individual fetchers?

Cheers,

Richard


  reply	other threads:[~2016-08-20 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 17:08 [PATCH v2] Fixes for fetcher cwd changes Matt Madison
2016-08-10 17:08 ` [PATCH v2] fetch2: preserve current working directory Matt Madison
2016-08-20 15:10   ` Richard Purdie [this message]
2016-08-21 13:09     ` Matt Madison

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=1471705829.16712.70.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=matt@madison.systems \
    /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.