git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Gray <aaronngray.lists@googlemail.com>
To: Peter Baumann <waste.manager@gmx.de>,
	Aaron Gray <aaronngray.lists@googlemail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Resetting working files
Date: Sun, 31 May 2009 17:50:35 +0100	[thread overview]
Message-ID: <9719867c0905310950x153db8efw179a8a10ac3f4640@mail.gmail.com> (raw)
In-Reply-To: <20090531163225.GE3674@debian.b2j>

2009/5/31 bill lam <cbill.lam@gmail.com>
>
> On Sun, 31 May 2009, Peter Baumann wrote:
> >       echo modified >> a.txt
> >       git add a.txt
> >       git checkout -- a.txt           (1)
> >
> >       git checkout HEAD -- a.txt      (2)
> >
> >
> > (1) This will do nothing to your file 'a.txt' in your workdir because
> >     the index and the workdir are identical
> >
> > (2) This will reset your file to the state before you run that bogus
> >     echo modified >> a.txt   comand
>
> I still do not understand what index is.
> 1. is index an replica of the committed tree
> 2. is index only transient in that its content will be reset once
>   committed?
> 3. or other ?

I think index is HEAD or a revision hash. Am I correct ?

Aaron

  parent reply	other threads:[~2009-05-31 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-31 13:09 Resetting working files Aaron Gray
2009-05-31 15:00 ` Dirk Süsserott
2009-05-31 15:57   ` Aaron Gray
2009-05-31 16:25   ` Peter Baumann
     [not found]     ` <20090531163225.GE3674@debian.b2j>
2009-05-31 16:50       ` Aaron Gray [this message]
2009-05-31 17:39         ` Nicolas Sebrecht
2009-05-31 19:31           ` Aaron Gray
2009-05-31 21:30           ` Alex Riesen

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=9719867c0905310950x153db8efw179a8a10ac3f4640@mail.gmail.com \
    --to=aaronngray.lists@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=waste.manager@gmx.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;
as well as URLs for NNTP newsgroup(s).