Git development
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] core-git documentation update
Date: Sun, 08 May 2005 22:26:02 +0100	[thread overview]
Message-ID: <427E83EA.2000104@dgreaves.com> (raw)
In-Reply-To: <7vd5s15up8.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

Junio C Hamano wrote:

>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.
>  
>
This merged fine.
Purely for editorial consistency I added "" around the command - see patch

The intention now was for me to go through Linus' HEAD and verify the
docs actually documented the HEAD.
Then I think comparing the HEAD to jit-jc and preparing patches for that?

>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?
>  
>
yes - that was just to assist people in reading the docs without having
to apply patches etc etc.

>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.
>  
>
I had hoped you'd pick this up in that manner - thanks

David
PS Removed Linus from cc

Add quotes for editorial consistency

Signed-off-by: David Greaves <david@dgreaves.com>
---




[-- Attachment #2: core-git_editorial.patch --]
[-- Type: text/x-patch, Size: 614 bytes --]

Documentation/core-git.txt: needs update
Index: Documentation/core-git.txt
===================================================================
--- 08cd7ce14ca4da7db37dce88e416e67b01f3452a/Documentation/core-git.txt  (mode:100644 sha1:e046119fcdd948dec81b11376ec9198e76a109af)
+++ uncommitted/Documentation/core-git.txt  (mode:100644)
@@ -503,7 +503,7 @@
 -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
+	"git-diff-cache" say that all non-checked-out files are up
 	to date.
 
 Output format

  reply	other threads:[~2005-05-08 21:19 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
2005-05-08 21:26   ` David Greaves [this message]
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=427E83EA.2000104@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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