Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Michał Górny <mgorny@g.o>
Subject: Re: [PATCH git-2.eclass 1/2] Clean up non-bare checkout before updating.
Date: Fri, 23 Dec 2011 22:49:46 +0100
On Fri, 23 Dec 2011 22:09:26 +0100
Ulrich Mueller <ulm@g.o> wrote:

> >>>>> On Fri, 23 Dec 2011, Michał Górny wrote:
> 
> > Fixes: https://bugs.gentoo.org/show_bug.cgi?id=395247
> 
> > +		git clean -d -f -x || die "${FUNCNAME}: failed to
> > clean checkout dir" +
> 
> Why should there be untracked files, in the first place? (In the
> "steps to reproduce" of bug 395247 such files are explicitly generated
> by the user, which doesn't look like a valid usage case to me.)

Yes, it is invalid. Yet I think it's better to clean up just in case
upstream pulling gone wrong (e.g. when upstream does rebase).

-- 
Best regards,
Michał Górny
Attachment:
signature.asc (PGP signature)
Replies:
Re: [PATCH git-2.eclass 1/2] Clean up non-bare checkout before updating.
-- Mike Frysinger
References:
[PATCH git-2.eclass 1/2] Clean up non-bare checkout before updating.
-- Michał Górny
Re: [PATCH git-2.eclass 1/2] Clean up non-bare checkout before updating.
-- Ulrich Mueller
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: [PATCH git-2.eclass 1/2] Clean up non-bare checkout before updating.
Next by thread:
Re: [PATCH git-2.eclass 1/2] Clean up non-bare checkout before updating.
Previous by date:
Re: [PATCH git-2.eclass 1/2] Clean up non-bare checkout before updating.
Next by date:
Automated Package Removal and Addition Tracker, for the week ending 2011-12-25 23h59 UTC


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.