git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Jon Loeliger <jdl@freescale.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Added documentation for few missing options.
Date: Mon, 05 Dec 2005 22:10:19 -0800	[thread overview]
Message-ID: <7vd5ka7o38.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <E1EjV8R-00014y-Sg@jdl.com> (Jon Loeliger's message of "Mon, 05 Dec 2005 23:13:03 -0600")

Jon Loeliger <jdl@freescale.com> writes:

> More $ shell prompts in examples.
> Minor English grammar improvements.
> Added a few "See Also"s.
> Use back-ticks on more command examples.
>
> Signed-off-by: Jon Loeliger <jdl@freescale.com>

Thanks.  You deserve to add your own name to the Documentation
section ;-).

Mostly note to myself...

> +EXAMPLES
> +--------
> +To update and refresh only the files already checked out::
> ++
> +----------------
> +$ git-checkout-index -n -f -a && git-update-index --ignore-missing --refresh
> +----------------

These days, "git-checkout-index -n -u -f -a" may a preferred
equivalent of the above.

> +OPTIONS
> +-------
> +--template=<template_directory>::
> +	Provide the directory in from which templates will be used.

? "use templates stored in the named directory" ?

> @@ -220,8 +222,8 @@ populated.  Here is an outline of how th
>      matching "stage1" entry if it exists too.  .. all the normal
>      trivial rules ..
>  
> -You would normally use "git-merge-index" with supplied
> -"git-merge-one-file" to do this last step.  The script
> +You would normally use `git-merge-index` with supplied
> +`git-merge-one-file` to do this last step.  The script
>  does not touch the files in the work tree, and the entire merge
>  happens in the index file.  In other words, there is no need to
>  worry about what is in the working directory, since it is never

The above paragraph is way out of date, as of beginning of June
2005.  The current merge-one-file does smudge the working tree
during the merge.  I'll rewrite it.

      reply	other threads:[~2005-12-06  6:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06  5:13 [PATCH] Added documentation for few missing options Jon Loeliger
2005-12-06  6:10 ` Junio C Hamano [this message]

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=7vd5ka7o38.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=jdl@freescale.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).