git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Documentation Directions
@ 2005-11-06 17:35 Jon Loeliger
  2005-11-06 20:11 ` Junio C Hamano
  2005-11-06 22:03 ` Nikolai Weibull
  0 siblings, 2 replies; 4+ messages in thread
From: Jon Loeliger @ 2005-11-06 17:35 UTC (permalink / raw)
  To: git

Couple of questions regarding documentation direction:

- Is the plan to update all docs to use $GIT_DIR instead of .git?

- Do we intend on adding explicit support for '--help' on most,
  if not all, of the git commands?  In some cases (git-branch)
  a -*) case tacitly catches --help and usage()'s it.  In other
  cases (git-pull) this can't be done as -*) passes options
  on to git-fetch.  I think that we should catch --help directly
  so that it doesn't emit git-fetch's *) catch-all usage:

    % git pull --help
    usage: git-fetch-pack [-q] [-v] [--exec=upload-pack] [host:]directory <refs>...
    Fetch failure: --help

- Do you want to head in the per-man-page-"Now What?" direction
  as suggested by Junio?

Thanks,
jdl

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Documentation Directions
@ 2005-11-06 19:28 Jon Loeliger
  0 siblings, 0 replies; 4+ messages in thread
From: Jon Loeliger @ 2005-11-06 19:28 UTC (permalink / raw)
  To: git


Also:

    - Do you want to standardize on using a '$' prompt
      for all the example command executions samples?
      Like so:

          Do do the thing, run the command:

                $ git-frobnicate --weirdly

Do you/we care?  Consistency uber alles?

Thanks,
jdl

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Documentation Directions
  2005-11-06 17:35 Documentation Directions Jon Loeliger
@ 2005-11-06 20:11 ` Junio C Hamano
  2005-11-06 22:03 ` Nikolai Weibull
  1 sibling, 0 replies; 4+ messages in thread
From: Junio C Hamano @ 2005-11-06 20:11 UTC (permalink / raw)
  To: Jon Loeliger; +Cc: git

Jon Loeliger <jdl@freescale.com> writes:

> Couple of questions regarding documentation direction:
>
> - Is the plan to update all docs to use $GIT_DIR instead of .git?

I personally feel we should use less (not more) $GIT_DIR in the
documentation and casual mention of things under .git/ directory
should say .git/ instead, with the understanding that the reader
have already learned that there is a way to override it if the
user chooses to do so.

> - Do we intend on adding explicit support for '--help' on most,
>   if not all, of the git commands?

I think that would be very helpful.

>     - Do you want to standardize on using a '$' prompt
>       for all the example command executions samples?

Ah, I see you recently added a couple of Csh style '%' prompt.
Also I suspect that some examples in earlier tutorial do not
even have any prompt.

You are right -- being consistent would be nice.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Documentation Directions
  2005-11-06 17:35 Documentation Directions Jon Loeliger
  2005-11-06 20:11 ` Junio C Hamano
@ 2005-11-06 22:03 ` Nikolai Weibull
  1 sibling, 0 replies; 4+ messages in thread
From: Nikolai Weibull @ 2005-11-06 22:03 UTC (permalink / raw)
  To: git

Jon Loeliger wrote:

> - Is the plan to update all docs to use $GIT_DIR instead of .git?

Well, shouldn't we go all the way and use ${GIT_DIR:-.git} then?  :-)

        nikolai

-- 
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-11-06 22:03 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-11-06 17:35 Documentation Directions Jon Loeliger
2005-11-06 20:11 ` Junio C Hamano
2005-11-06 22:03 ` Nikolai Weibull
  -- strict thread matches above, loose matches on Subject: below --
2005-11-06 19:28 Jon Loeliger

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).