git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Enrico Weigelt <weigelt@metux.de>
To: git@vger.kernel.org
Subject: Re: checkout w/ removing untracked files
Date: Mon, 23 Aug 2010 14:12:30 +0200	[thread overview]
Message-ID: <20100823121229.GA12810@nibiru.local> (raw)
In-Reply-To: <7v39ubaedg.fsf@alter.siamese.dyndns.org>

* Junio C Hamano <gitster@pobox.com> wrote:
> Enrico Weigelt <weigelt@metux.de> writes:
> 
> > For my Briegel buildsystem (git://pubgit.metux.de/projects/briegel.git/)
> > I need to checkout a really tree (iow: no untracked files may be
> > left in the workdir) from git. ATM I'm removing and recreating the
> > whole directory first, but I hope to get rid of this step.
> 
> (1) If you have a correctly working "make reallyclean" to remove build
>     artifacts, you wouldn't even need such an option.

I can't rely on that. Some of the trees aren't even sourcetrees 
but sysroot images. I need a guaranteed fresh tree w/o any 
user intervention.


> (2) Have you tried to read up on "git clean -dfqx"?

Thanks, that should do it :)


cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt@metux.de
 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------

      reply	other threads:[~2010-08-23 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 19:31 checkout w/ removing untracked files Enrico Weigelt
2010-08-18 19:51 ` Junio C Hamano
2010-08-23 12:12   ` Enrico Weigelt [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100823121229.GA12810@nibiru.local \
    --to=weigelt@metux.de \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).