git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Liu Yubao" <yubao.liu@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: how to revert changes in working tree?
Date: Wed, 6 Dec 2006 09:43:27 +0100	[thread overview]
Message-ID: <81b0412b0612060043t488d356du8f5fcdd164a45eb5@mail.gmail.com> (raw)
In-Reply-To: <4576680B.7030500@gmail.com>

On 12/6/06, Liu Yubao <yubao.liu@gmail.com> wrote:
> I'm confused how to revert changes in working tree:
>
> $ git fetch
> $ git merge "sync with origin" HEAD origin
> ....conflict....

You may want to consider git pull. It'd do exactly the same

> $ git branch
> * master
>   origin
>
> $ git status
> # .....: needs update
> # .....: needs update
> (In fact I never modified anything in this tree, and "git diff"
> showed many difference indeed, very strange).

That's windows and cygwin for you. They work together
and may someday even figure how to commit the changes.

They problem is the exec-bit which windows does not
have and cygwin failed to correctly workaround the
limitation.

Do a "git repo-config core.filemode false" to almost
disable the checks for exec bit.

> I tried "git update-index --refresh", "git reset --hard",
> "git reset --hard master", "git checkout master",
> "git checkout -f master", but "git status" still said same
> as above.

After git update-index --refresh you shouldn't have had
the diffs (unless you actually had textual changes).

> At last, I deleted all files that were reported to be updated
> with "rm -rf", ran "git checkout master" and "git status", then
> git reported:
> #       deleted:    ....
> #       deleted:    ....

Now do a git reset --hard and you should be set,
unless you're unlucky enough to work on FAT,
where probably nothing will save you.

And avoid using any "special" characters (8bit, utf/unicode)
in filenames, while you're on windows: you'll never be able
to share the repository (unless others agree to use your

  reply	other threads:[~2006-12-06  8:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06  6:49 how to revert changes in working tree? Liu Yubao
2006-12-06  8:43 ` Alex Riesen [this message]
2006-12-06  9:57   ` Liu Yubao
2006-12-06 10:20     ` Alex Riesen
2006-12-06 11:14       ` Liu Yubao
2006-12-06 12:30         ` Alex Riesen
2006-12-06 12:52         ` Jakub Narebski
2006-12-06 18:13         ` Shawn Pearce
2006-12-07  1:42           ` Liu Yubao
2006-12-07  7:15             ` Juergen Ruehle
2006-12-06 10:20     ` Jakub Narebski

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=81b0412b0612060043t488d356du8f5fcdd164a45eb5@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=yubao.liu@gmail.com \
    /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).