From: Thomas Rast <trast@student.ethz.ch>
To: <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v2 0/5] git-reset documentation changes
Date: Sun, 18 Jul 2010 20:23:21 +0200 [thread overview]
Message-ID: <cover.1279477130.git.trast@student.ethz.ch> (raw)
In-Reply-To: <7v7hkvrwd0.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
[on patch 2/5]
> > DESCRIPTION
> > -----------
> > +Sets the current branch to the specified <commit> and optionally
> > +resets the index and working tree to match. The <commit> defaults to
> > +HEAD in all forms.
>
> With a careless reading of this paragraph, I got an impression that HEAD
> is always affected, but I happen to know that is not the case ;-).
>
> - "reset" is primarily about resetting the index and the --soft option
> can be used to optionally not to do this.
>
> . with paths, the command is about fixing up the index contents for
> given specific paths, to prepare for the next commit. HEAD is not
> moved.
>
> . without paths, the command is about changing what commit to build
> your next commit on, i.e. HEAD is moved.
You're right, I completely left out the <paths> mode there. I rewrote
this as a short summary of all three modes in this version.
> "git reset HEAD frotz" from a head commit without frotz gets rid of frotz
> from the index, no?
True. I thought it didn't (and required rm --cached) but I must have
mixed up something.
The other patches are unchanged from v1.
Thomas Rast (5):
Documentation/git-reset: reorder modes for soft-mixed-hard
progression
Documentation/reset: separate options by mode
Documentation/reset: promote 'examples' one section up
Documentation/reset: reorder examples to match description
Documentation/reset: move "undo permanently" example behind "make
topic"
Documentation/git-reset.txt | 347 ++++++++++++++++++++++---------------------
1 files changed, 178 insertions(+), 169 deletions(-)
--
1.7.2.rc3.317.gc287
next prev parent reply other threads:[~2010-07-18 18:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 9:44 [RFC PATCH 0/5] git-reset documentation changes Thomas Rast
2010-07-16 9:44 ` [RFC PATCH 1/5] Documentation/git-reset: reorder modes for soft-mixed-hard progression Thomas Rast
2010-07-16 9:44 ` [RFC PATCH 2/5] Documentation/reset: separate options by mode Thomas Rast
2010-07-16 20:43 ` Junio C Hamano
2010-07-18 18:23 ` Thomas Rast [this message]
2010-07-18 18:23 ` [PATCH v2 1/5] Documentation/git-reset: reorder modes for soft-mixed-hard progression Thomas Rast
2010-07-18 18:23 ` [PATCH v2 2/5] Documentation/reset: separate options by mode Thomas Rast
2010-07-18 18:23 ` [PATCH v2 3/5] Documentation/reset: promote 'examples' one section up Thomas Rast
2010-07-18 18:23 ` [PATCH v2 4/5] Documentation/reset: reorder examples to match description Thomas Rast
2010-07-18 18:23 ` [PATCH v2 5/5] Documentation/reset: move "undo permanently" example behind "make topic" Thomas Rast
2010-07-16 9:44 ` [RFC PATCH 3/5] Documentation/reset: promote 'examples' one section up Thomas Rast
2010-07-16 9:44 ` [RFC PATCH 4/5] Documentation/reset: reorder examples to match description Thomas Rast
2010-07-16 9:44 ` [RFC PATCH 5/5] Documentation/reset: move "undo permanently" example behind "make topic" Thomas Rast
2010-07-16 21:00 ` [RFC PATCH 0/5] git-reset documentation changes 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=cover.1279477130.git.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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.