From: Bahadir Balban <bahadir.balban@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: reverting back both working copy and commits
Date: Thu, 12 Jan 2006 10:40:07 +0000 [thread overview]
Message-ID: <7ac1e90c0601120240u3f8d7571g5e5bf52b6d3c4c2a@mail.gmail.com> (raw)
In-Reply-To: <7vslrutv2h.fsf@assigned-by-dhcp.cox.net>
On 1/11/06, Junio C Hamano <junkio@cox.net> wrote:
> Eh? That should not happen.
>
> Could you elaborate?
> What "git reset --hard" would leave behind are files in the
> working tree that you had when you made the wrongly done commit,
> which were *not* known to git (i.e. you forgot to "git add"
> before committing). Since they are not known to git, "reset --hard"
> does not touch them.
Sorry, it's my mistake, I later realised the working tree had been
updated correctly.
Thanks,
Bahadir
prev parent reply other threads:[~2006-01-12 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 16:32 reverting back both working copy and commits Bahadir Balban
2006-01-11 19:28 ` Andreas Ericsson
2006-01-11 19:37 ` Junio C Hamano
2006-01-12 10:40 ` Bahadir Balban [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ac1e90c0601120240u3f8d7571g5e5bf52b6d3c4c2a@mail.gmail.com \
--to=bahadir.balban@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).