All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Jan Hudec <bulb@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] user-manual: Talk about tracking third-party snapshots
Date: Sat, 17 Nov 2007 20:54:01 +0100	[thread overview]
Message-ID: <200711172054.02746.jnareb@gmail.com> (raw)
In-Reply-To: <20071117191846.GE5198@efreet.light.src>

Jan Hudec wrote:
> On Sat, Nov 17, 2007 at 19:18:40 +0100, Jakub Narebski wrote:
>> On Sat, Nov 17, 2007, Jan Hudec wrote:

>>> git log has such option?
>>> 
>>> $ man git-log | grep -e --left-right; echo $?
>>> 1
>>> $ git --version
>>> git version 1.5.3.5
>> 
>> It has, although it is hidden in git-rev-list(1) manpage. It is a bit
>> obscure corner...
> 
> I hope the new option parsing ifrastructure will take over quickly and start
> to be used to generate the short help and probably even option section in the
> man pages. It's unfortunately not the only option that is not mentioned in
> the manual page of a command that has it.

Truth to be told _this_ one option I don't mean it is only
in git-rev-parse (which git-log references, together with git-diff)

-- 
Jakub Narebski
Poland

  reply	other threads:[~2007-11-17 19:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 12:29 [PATCH] user-manual: Talk about tracking third-party snapshots Michael Smith
2007-11-13 14:07 ` Jakub Narebski
2007-11-13 15:30   ` Sergei Organov
2007-11-13 15:38     ` Jakub Narebski
2007-11-17 16:45   ` Jan Hudec
2007-11-17 18:18     ` Jakub Narebski
2007-11-17 19:18       ` Jan Hudec
2007-11-17 19:54         ` Jakub Narebski [this message]
2007-11-13 19:25 ` Junio C Hamano
2007-11-13 21:37   ` Michael Smith
2007-11-19  1:17   ` J. Bruce Fields
2007-11-19  0:48 ` J. Bruce Fields

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=200711172054.02746.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=bulb@ucw.cz \
    --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.