From: Salikh Zakirov <Salikh.Zakirov@Intel.com>
To: git@vger.kernel.org
Subject: Re: Restore a single file in the index back to HEAD
Date: Thu, 02 Nov 2006 15:47:17 +0300 [thread overview]
Message-ID: <eicpch$7ar$2@sea.gmane.org> (raw)
In-Reply-To: <7vbqnq51v4.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> In other words, I do not have a good explanation on what "git
> reset [--hard|--mixed] <commit> <path>..." does that I can write
> in the documentation.
In my humble opinion, git-reset is somewhat overloaded in functionality,
and it takes time to explain its function to git newbies.
Why not split it into two commands, e.g.
git-rewind for manipulations with HEAD
git-reset for manipulations with index and working copy only
?
next prev parent reply other threads:[~2006-11-02 12:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 15:41 Restore a single file in the index back to HEAD Andy Parkins
2006-10-26 15:42 ` Alex Riesen
2006-10-27 7:27 ` Andy Parkins
2006-10-27 7:38 ` Shawn Pearce
2006-10-27 8:01 ` Andy Parkins
2006-10-27 8:08 ` Andreas Ericsson
2006-10-27 8:15 ` Shawn Pearce
2006-10-27 9:45 ` Alex Riesen
2006-10-27 9:50 ` Andreas Ericsson
2006-10-27 10:02 ` Junio C Hamano
2006-10-27 17:45 ` Luben Tuikov
2006-11-01 7:58 ` Nguyen Thai Ngoc Duy
2006-11-01 8:07 ` Junio C Hamano
2006-11-01 8:34 ` Junio C Hamano
2006-11-01 9:09 ` Nguyen Thai Ngoc Duy
2006-11-01 11:22 ` Jakub Narebski
2006-11-01 9:38 ` Jakub Narebski
2006-11-01 8:39 ` Andy Parkins
2006-11-01 8:56 ` Junio C Hamano
2006-11-01 9:53 ` Andy Parkins
2006-11-01 18:28 ` Junio C Hamano
2006-11-01 20:29 ` Andy Parkins
2006-11-01 20:49 ` Junio C Hamano
2006-11-01 21:18 ` Andy Parkins
2006-11-01 22:08 ` Junio C Hamano
2006-11-01 23:09 ` Andy Parkins
2006-11-01 23:39 ` Junio C Hamano
2006-11-02 8:44 ` Andy Parkins
2006-11-01 22:27 ` Robin Rosenberg
2006-11-02 12:47 ` Salikh Zakirov [this message]
2006-10-27 9:03 ` [PATCH] Added description for inverting git-update-index using --index-info Andy Parkins
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='eicpch$7ar$2@sea.gmane.org' \
--to=salikh.zakirov@intel.com \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.