public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce•org>
To: Chris Lee <clee@kde•org>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: Simple UI question...
Date: Sun, 7 Jan 2007 06:29:45 -0500	[thread overview]
Message-ID: <20070107112944.GF10351@spearce.org> (raw)
In-Reply-To: <204011cb0701070321w18942a3w7fb4f7ecd26fc457@mail.gmail.com>

Chris Lee <clee@kde•org> wrote:
> Eric's shows the same problem - for some revision IDs, when I do a
> checkout, I only get the files that were changed in that revision.
> 
> >If Eric's version isn't always working then I'd have to suggest
> >that you exmaine the output of `git status` for switching to
> >some temporary branch based on $sha1sum.  Perhaps you have local
> >modifications which are carrying over in your working directory?
> 
> I assume 'removing everything in the working tree' counts as "local
> modifications"? :)

Yes!  That's what's going wrong.  Don't do "rm -rf *".  Let Git take
care of the empty directories for you.  If Git deletes all source
files in that directory (as they don't belong in this version that
you are checking out) it will also delete the now empty directory.

The only time it fails is if you are on Windows and some process
has the directory busy.  :-)

-- 
Shawn.

  reply	other threads:[~2007-01-07 11:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-07 11:02 Simple UI question Chris Lee
2007-01-07 11:06 ` Josef "Jeff" Sipek
2007-01-07 11:13 ` Shawn O. Pearce
2007-01-07 11:21   ` Chris Lee
2007-01-07 11:29     ` Shawn O. Pearce [this message]
2007-01-07 11:38       ` Chris Lee
2007-01-07 11:40         ` Junio C Hamano
2007-01-07 11:50           ` Chris Lee
2007-01-07 11:30 ` Junio C Hamano

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=20070107112944.GF10351@spearce.org \
    --to=spearce@spearce$(echo .)org \
    --cc=clee@kde$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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