git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Jonathan Nieder <jrnieder@uchicago.edu>,
	git@vger.kernel.org, Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
	Jon Loeliger <jdl@jdl.com>
Subject: Re: [PATCH 3/7] Documentation: complicate example of "man git-command"
Date: Thu, 3 Jul 2008 08:06:37 +0200	[thread overview]
Message-ID: <200807030806.37771.chriscool@tuxfamily.org> (raw)
In-Reply-To: <7vmyl1kvn6.fsf@gitster.siamese.dyndns.org>

Le mercredi 2 juillet 2008, Junio C Hamano a écrit :
>
> 	E.g. a typical command description may go like this:
>
>         To propagate the changes you made back to the original subversion
>         repository, you would use 'git-svn dcommit' command.  It does
>         these things (long description here).  Some examples:

We might kill 2 birds with a single stone by describing "git help" instead 
of "git svn" (that the user may never use).

>         ------------
> 	$ ... some example command sequence ...
>         $ git svn dcommit
>         ------------
>
>         For full details, type:
>
> 	------------
>         $ man git-svn
>         ------------

I saw that in another thread "git help" is also being ported to Windows and 
I wonder if we want the tutorial to be usable as is by people on Windows 
too.

I mean what if people on Windows launch "git help tutorial"? Should they see 
nothing or a tutorial for *nix or a special version of the tutorial for 
Windows or a tutorial that works everywhere? I think the latter would be 
best but I wonder if it is possible.

Anyway if we want to get there, perhaps we should use "git help svn" above 
instead of "man git-svn". (Yeah "git help help" might be confusing at 
first.)

Thanks,
Christian.

  

  parent reply	other threads:[~2008-07-03  8:25 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30 21:56 [PATCH 0/7] Some superficial documentation changes Jonathan Nieder
2008-06-30 22:01 ` [PATCH 1/7] Documentation: fix links to tutorials and other new manual pages Jonathan Nieder
2008-06-30 23:30   ` Christian Couder
2008-06-30 22:05 ` [PATCH 2/7] whitespace fix in Documentation/git-repack.txt Jonathan Nieder
2008-06-30 22:10 ` [PATCH 3/7] Documentation: complicate example of "man git-command" Jonathan Nieder
2008-06-30 23:39   ` Christian Couder
2008-07-01 16:23   ` J. Bruce Fields
2008-07-01 23:54     ` Junio C Hamano
2008-07-02 21:31       ` J. Bruce Fields
2008-07-03  1:45         ` Jonathan Nieder
2008-07-03 18:18           ` J. Bruce Fields
2008-07-03  6:06       ` Christian Couder [this message]
2008-07-03  7:44         ` Junio C Hamano
2008-06-30 22:15 ` [PATCH 4/7] git-daemon(1): don't assume git-daemon is in /usr/bin Jonathan Nieder
2008-06-30 22:17 ` [PATCH 5/7] Documentation: prepare to be consistent about "git-" versus "git " Jonathan Nieder
2008-06-30 22:29   ` [PATCH 6/7] Documentation: " Jonathan Nieder
2008-06-30 22:36 ` [RFC/PATCH 7/7] Documentation formatting and cleanup Jonathan Nieder
2008-07-01 13:09   ` Olivier Marin
2008-07-01 21:34     ` Junio C Hamano
2008-07-03  2:09       ` Jonathan Nieder
2008-07-03  2:28     ` Jonathan Nieder
2008-07-01  8:42 ` [PATCH 0/7] Some superficial documentation changes Junio C Hamano
2008-07-03  4:31   ` Jonathan Nieder
2008-07-03  4:47     ` [PATCH 01/15] git-format-patch(1): fix stray \ in output Jonathan Nieder
2008-07-03  4:54     ` [PATCH 02/15] Documentation: fix gitlinks Jonathan Nieder
2008-07-03  5:03     ` [PATCH 03/15] manpages: fix bogus whitespace Jonathan Nieder
2008-07-03 23:55       ` Junio C Hamano
2008-07-04  1:14         ` Jonathan Nieder
2008-07-03  5:08     ` [PATCH 04/15] git(1): add comma Jonathan Nieder
2008-07-03  5:13     ` [PATCH 05/15] git-commit(1): depersonalize description Jonathan Nieder
2008-07-03  5:20     ` [PATCH 06/15] Documentation: rewrap to prepare for "git-" vs "git " change Jonathan Nieder
2008-07-03  5:28     ` [PATCH 07/15] Documentation: more "git-" versus "git " changes Jonathan Nieder
2008-07-03  5:30     ` [PATCH 08/15] gitdiffcore(7): fix awkward wording Jonathan Nieder
2008-07-03  5:36     ` [PATCH 09/15] manpages: italicize command names in synopses Jonathan Nieder
2008-07-03  5:37     ` [PATCH 10/15] manpages: italicize command names Jonathan Nieder
2008-07-03  5:45     ` [PATCH 11/15] manpages: italicize git command names (which were in teletype font) Jonathan Nieder
2008-07-03  5:49     ` [PATCH 12/15] manpages: italicize gitk's name (where it was " Jonathan Nieder
2008-07-03  5:55     ` [PATCH 13/15] manpages: italicize nongit command names (if they are " Jonathan Nieder
2008-07-03  5:59     ` [PATCH 14/15] manpages: italicize git subcommand names (which were " Jonathan Nieder
2008-07-03  6:06     ` [PATCH 15/15] manpages: use teletype font for sample command lines Jonathan Nieder

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=200807030806.37771.chriscool@tuxfamily.org \
    --to=chriscool@tuxfamily.org \
    --cc=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jdl@jdl.com \
    --cc=jrnieder@uchicago.edu \
    --cc=pclouds@gmail.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 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).