From: Chuck Lever <cel@citi.umich.edu>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: documentation issues
Date: Thu, 01 Dec 2005 17:06:21 -0500 [thread overview]
Message-ID: <438F73DD.2000203@citi.umich.edu> (raw)
In-Reply-To: <7v64q8fqm8.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
Junio C Hamano wrote:
>>also, git-diff-index supports a "-r" option, but that doesn't seem to be
>>documented on this page.
>
>
> What Chris Shoemaker said is right.
>
> But we could do this instead if you want. I am neutral myself.
thanks for clarifying.
StGIT does use "git-diff-index -r" in git.__tree_status(). i think it
can be safely removed.
[-- Attachment #2: cel.vcf --]
[-- Type: text/x-vcard, Size: 445 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Charles
org:Network Appliance, Incorporated;Open Source NFS Client Development
adr:535 West William Street, Suite 3100;;Center for Information Technology Integration;Ann Arbor;MI;48103-4943;USA
email;internet:cel@citi.umich.edu
title:Member of Technical Staff
tel;work:+1 734 763 4415
tel;fax:+1 734 763 4434
tel;home:+1 734 668 1089
x-mozilla-html:FALSE
url:http://www.monkey.org/~cel/
version:2.1
end:vcard
next prev parent reply other threads:[~2005-12-01 22:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 20:28 documentation issues Chuck Lever
2005-12-01 20:34 ` Chris Shoemaker
2005-12-01 21:34 ` Junio C Hamano
2005-12-01 21:54 ` Chris Shoemaker
2005-12-01 22:06 ` Chuck Lever [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-28 22:34 Documentation Issues Tom King
2011-11-30 9:02 ` bernhard.guillon
2016-07-05 21:17 documentation issues Xen
2016-07-06 0:57 ` Ian Kent
2016-07-06 4:47 ` Xen
2016-07-06 12:48 ` Ian Kent
2016-07-06 12:53 ` Erwan Loaec
2016-07-10 17:07 ` Xen
2016-07-11 14:09 ` Ian Kent
2016-07-13 2:17 ` Marion, Mike
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=438F73DD.2000203@citi.umich.edu \
--to=cel@citi.umich.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.