Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: David Greaves <david@dgreaves.com>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH 0/2] core-git documentation update
Date: Sun, 08 May 2005 13:28:03 -0700	[thread overview]
Message-ID: <7vd5s15up8.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <427E4AE1.2040105@dgreaves.com> (David Greaves's message of "Sun, 08 May 2005 18:22:41 +0100")

David, thanks for taking time to update the document.  I ended
up hand merging your two patches since I had a bit more
documentation updates in git-jc tree, so I'd like you to
proofread the result.  

It is my understanding that if I have a correct patch result
from your patch 1 and patch 2, I can throw away this message:

    Subject: [FILES] core-git documentation update

Am I correct?

I intend to keep not-so-controvercial stuff in git-jc tree, so
that when Linus returns he can pull from it instead of patching
from a pile of e-mails, potentially risking to leave good stuff
in his mailbox during that process.

The following diff is between:

    - Linus tree with two patches from you
    + The result of my hand merge, which I intend to ask Linus
      to pull when he returns.

Thanks.
---

# - 2: As Greaves
# + (working tree)
--- a/Documentation/core-git.txt
+++ b/Documentation/core-git.txt
@@ -473,7 +473,7 @@ git-diff-cache - Compares content and mo
 
 SYNOPSIS
 --------
-'git-diff-cache' [-p] [-r] [-z] [--cached] <tree-ish>
+'git-diff-cache' [-p] [-r] [-z] [-m] [--cached] <tree-ish>
 
 DESCRIPTION
 -----------
@@ -500,6 +500,12 @@ OPTIONS
 --cached::
 	do not consider the on-disk file at all
 
+-m::
+	By default, files recorded in the index but not checked
+	out are reported as deleted.  This flag makes
+	git-diff-cache say that all non-checked-out files are up
+	to date.
+
 Output format
 -------------
 include::diff-format.txt[]
@@ -1515,7 +1521,7 @@ git-update-cache - Modifies the index or
 SYNOPSIS
 --------
 'git-update-cache'
-	     [--add] [--remove] [--refresh]
+	     [--add] [--remove] [--refresh] [--replace]
 	     [--ignore-missing]
 	     [--force-remove <file>]
 	     [--cacheinfo <mode> <object> <file>]\*
@@ -1556,6 +1562,14 @@ OPTIONS
 	Remove the file from the index even when the working directory
 	still has such a file.
 
+--replace::
+	By default, when a file `path` exists in the index,
+	git-update-cache refuses an attempt to add `path/file`.
+	Similarly if a file `path/file` exists, a file `path`
+	cannot be added.  With --replace flag, existing entries
+	that conflicts with the entry being added are
+	automatically removed with warning messages.
+
 --::
 	Do not interpret any more arguments as options.
 



  parent reply	other threads:[~2005-05-08 20:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-08 17:22 [PATCH 0/2] core-git documentation update David Greaves
2005-05-08 19:38 ` Junio C Hamano
2005-05-08 21:01   ` David Greaves
2005-05-08 20:28 ` Junio C Hamano [this message]
2005-05-08 21:26   ` David Greaves
2005-05-08 23:35     ` Junio C Hamano

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=7vd5s15up8.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=david@dgreaves.com \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.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