git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Benoit Sigoure <tsuna@lrde.epita.fr>
Cc: Lars Hjemli <hjemli@gmail.com>,
	Jonas Juselius <jonas.juselius@chem.uit.no>,
	git@vger.kernel.org
Subject: Re: Git in a Nutshell guide
Date: Mon, 19 Nov 2007 13:13:58 -0500	[thread overview]
Message-ID: <20071119181358.GG10450@fieldses.org> (raw)
In-Reply-To: <25CF3422-A236-46CE-B243-3F01117B7743@lrde.epita.fr>

On Mon, Nov 19, 2007 at 07:10:07PM +0100, Benoit Sigoure wrote:
> On Nov 19, 2007, at 6:04 PM, Lars Hjemli wrote:
>
>> On Nov 19, 2007 5:57 PM, Benoit Sigoure <tsuna@lrde.epita.fr> wrote:
>>> Understanding this is very important because ``error humanum est'',
>>> and people happen to screw up their hard work and they don't realize
>>> that they can go back without even knowing what the hell the reflog
>>> is or how to use it (I personally don't know -- but I'd like to, give
>>> me pointers please :D).
>>
>> You can simply try 'git reflog', and then 'man git-reflog' ;-)
>
> Did you only read the man?  It doesn't explain how to use the reflog or I 
> must have a very hard time understanding it.  I don't know where the 
> HEAD@{N} syntax is documented, but surely not in man git-reflog.

My copy at least has this paragraph:

	The subcommand "show" (which is also the default, in the absence of any
       subcommands) will take all the normal log options, and show the log of
       HEAD, which will cover all recent actions, including branch switches.
       It is basically an alias for git log -g --abbrev-commit
       --pretty=oneline, see git-log(1).

But, yeah, HEAD@{N} isn't documented there or in git-log(1), it's in
git-rev-parse(1).  I agree that the git-reflog manpage should at least
reference all of this, as it's the obvious first place people will go to learn
about reflogs....

--b.

  reply	other threads:[~2007-11-19 18:14 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 13:05 Git in a Nutshell guide Jonas Juselius
2007-11-19 13:29 ` Jakub Narebski
2007-11-19 14:33   ` Jonas Juselius
2007-11-22  8:22   ` David Kågedal
2007-11-23  9:28     ` Jakub Narebski
2007-11-19 15:02 ` Brian Downing
2007-11-19 15:03   ` Brian Downing
2007-11-19 15:48   ` Nicolas Pitre
2007-11-19 16:05 ` Jakub Narebski
2007-11-19 16:14   ` Jonas Juselius
2007-11-19 16:49     ` Benoit Sigoure
2007-11-19 22:01       ` Daniel Barkalow
2007-11-20 11:34       ` Jonas Juselius
2007-11-20 23:57       ` Jakub Narebski
2007-11-21 19:45         ` Jan Hudec
2007-11-21 21:32           ` Jakub Narebski
2007-11-22 16:37             ` jhud7196
2007-11-22 13:15   ` Jonas Juselius
2007-11-22 14:19     ` Jonathan del Strother
2007-11-22 14:24     ` Johannes Schindelin
2007-11-22 16:57     ` jhud7196
2007-11-19 16:45 ` Lars Hjemli
2007-11-19 16:56   ` Jonas Juselius
2007-11-19 16:57   ` Benoit Sigoure
2007-11-19 17:04     ` Lars Hjemli
2007-11-19 18:10       ` Benoit Sigoure
2007-11-19 18:13         ` J. Bruce Fields [this message]
2007-11-19 18:13         ` Matthieu Moy
2007-11-19 18:35           ` [PATCH] Doc fix for git-reflog: mention @{...} syntax, and <ref> in synopsys Matthieu Moy
2007-11-19 20:13             ` Junio C Hamano
2007-11-19 20:28               ` Matthieu Moy
2007-11-19 20:31                 ` Matthieu Moy
2007-11-19 21:15           ` Git in a Nutshell guide Benoit Sigoure
2007-11-19 21:33             ` Matthieu Moy
2007-11-19 21:51               ` Benoit Sigoure
2007-11-19 22:23                 ` J. Bruce Fields
2007-11-19 22:29                 ` Junio C Hamano
2007-11-19 22:59                   ` Matthieu Moy
2007-11-19 23:07                     ` Junio C Hamano
2007-11-19 17:05     ` Matthieu Moy

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=20071119181358.GG10450@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=hjemli@gmail.com \
    --cc=jonas.juselius@chem.uit.no \
    --cc=tsuna@lrde.epita.fr \
    /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).