From: Andy Whitcroft <apw@shadowen.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Han-Wen Nienhuys <hanwen@xs4all.nl>, git@vger.kernel.org
Subject: Re: [PATCH] git-reset --hard: tell the user what the HEAD was reset to
Date: Wed, 03 Jan 2007 13:17:21 +0000 [thread overview]
Message-ID: <459BACE1.5020406@shadowen.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0612211525070.19693@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
> ---
>
> On Wed, 20 Dec 2006, Han-Wen Nienhuys wrote:
>
> > It would be nice if git-reset printed
> >
> > HEAD is now <sha1> - <excerpt of commit message>
>
> This patch does that, but only for --reset.
>
> Without reset, HEAD is _not_ changed, just the contents of the
> working directory and/or the index.
>
> git-reset.sh | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/git-reset.sh b/git-reset.sh
> index 8d95e37..2379db0 100755
> --- a/git-reset.sh
> +++ b/git-reset.sh
> @@ -86,7 +86,12 @@ update_ref_status=$?
>
> case "$reset_type" in
> --hard )
> - ;; # Nothing else to do
> + test $update_ref_status = 0 && {
> + echo -n "HEAD is now at "
> + GIT_PAGER= git log --max-count=1 --pretty=oneline \
> + --abbrev-commit HEAD
> + }
> + ;;
> --soft )
> ;; # Nothing else to do
> --mixed )
Ok, this sounds like a good change in principle, but the output format
it introduces seems likely to cause confusion. For sure the first
couple of times I saw it I though there was a bug and I was seeing an
error from the plumbing. See below for an example where you would swear
something bad had occured.
apw@pinky$ git checkout -b bar master
apw@pinky$ git reset --hard ac9c1108d8915f0937795e354ad72c4ae6890a3f
HEAD is now at ac9c110... git-fetch: remove .keep file at the end.
Huh, fetch? Remove what .keep file? Did I do a fetch? What?
I think we need to delimit the name better, probabally we need to quote
it. Perhaps something like:
HEAD is now at ac9c110: "git-fetch: remove .keep file at the end".
-apw
next prev parent reply other threads:[~2007-01-03 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 22:55 UI nitpick Han-Wen Nienhuys
2006-12-21 14:26 ` [PATCH] git-reset --hard: tell the user what the HEAD was reset to Johannes Schindelin
2007-01-03 13:17 ` Andy Whitcroft [this message]
2007-01-04 12:59 ` Johannes Schindelin
2007-01-04 15:59 ` Andy Whitcroft
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=459BACE1.5020406@shadowen.org \
--to=apw@shadowen.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/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).