git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/git-commit: rewrite to make it more end-user friendly.
Date: Sat, 09 Dec 2006 23:05:04 +0100	[thread overview]
Message-ID: <elfbq4$tka$1@sea.gmane.org> (raw)
In-Reply-To: 7vpsas91e5.fsf@assigned-by-dhcp.cox.net

Junio C Hamano wrote:

> Nicolas Pitre <nico@cam.org> writes:

>>>  -o|--only::
>>> -   Commit only the files specified on the command line.
>>> -   This format cannot be used during a merge, nor when the
>>> -   index and the latest commit does not match on the
>>> -   specified paths to avoid confusion.
>>> +   Commit only the files specified on the command line;
>>> +   this is the default when pathnames are given on the
>>> +   command line, so you usually do not have to give this
>>> +   option.  This format cannot be used during a merge.
>>
>> Is there some value in keeping this option documented?  What about 
>> removing it (the documentation not the option)?
> 
> True, although the description of <files>... need to be
> clarified if we do this.

I'm a bit uncomfortable about removing documentation to existing
(if no-op) option. I'd rather it stay.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git


  reply	other threads:[~2006-12-09 22:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 11:20 Documentation/git-commit.txt Junio C Hamano
2006-12-08 11:55 ` Documentation/git-commit.txt Salikh Zakirov
2006-12-08 19:31   ` Documentation/git-commit.txt Junio C Hamano
2006-12-08 19:45     ` Documentation/git-commit.txt Nicolas Pitre
2006-12-08 22:56   ` Documentation/git-commit.txt Alan Chandler
2006-12-10  0:11     ` Documentation/git-commit.txt Horst H. von Brand
2006-12-10  9:23       ` Documentation/git-commit.txt Alan Chandler
2006-12-11 14:58         ` Documentation/git-commit.txt Andreas Ericsson
2006-12-09  2:58 ` Documentation/git-commit.txt Nicolas Pitre
2006-12-09  4:25   ` Documentation/git-commit.txt Junio C Hamano
2006-12-09  4:42     ` Documentation/git-commit.txt J. Bruce Fields
2006-12-09 19:58     ` Documentation/git-commit.txt Nicolas Pitre
2006-12-09 20:49       ` Documentation/git-commit.txt Jakub Narebski
2006-12-09  5:48   ` [PATCH] Documentation/git-commit: rewrite to make it more end-user friendly Junio C Hamano
2006-12-09 21:15     ` Nicolas Pitre
2006-12-09 21:59       ` Junio C Hamano
2006-12-09 22:05         ` Jakub Narebski [this message]
2006-12-09 22:19           ` Linus Torvalds
2006-12-09 22:24             ` Jakub Narebski
2006-12-09 22:26         ` Nicolas Pitre
2006-12-10  0:30     ` Josef Weidendorfer
2006-12-10  0:51       ` Nicolas Pitre
2006-12-10 21:00       ` J. Bruce Fields
2006-12-10 22:07         ` Nicolas Pitre
2006-12-10 22:41           ` J. Bruce Fields
2006-12-10 23:05           ` Junio C Hamano
2006-12-10  9:17     ` Alan Chandler
2006-12-09  4:31 ` Documentation/git-commit.txt 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='elfbq4$tka$1@sea.gmane.org' \
    --to=jnareb@gmail.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 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).