From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Added description for reversing git-update-index using --index-info
Date: Fri, 3 Nov 2006 09:21:52 +0100 [thread overview]
Message-ID: <200611030821.54350.andyparkins@gmail.com> (raw)
In-Reply-To: <7vfyd1mew3.fsf@assigned-by-dhcp.cox.net>
On Friday 2006 November 03 02:40, Junio C Hamano wrote:
> > +git ls-tree -r HEAD | git update-index --index-info
>
> While this is correct in the mechanical sense, it _sucks_ as an
> example, especially since you do not mention that the user would
> most likely need to do 'git update-index --refresh' afterwards
> to make the result useful.
I'm happy to ditch it if you wish; I included it only because it was one of
the examples that Shawn gave me in my original question.
Would you like a new patch?
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
prev parent reply other threads:[~2006-11-03 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 11:13 [PATCH] Added description for reversing git-update-index using --index-info Andy Parkins
2006-11-03 2:40 ` Junio C Hamano
2006-11-03 8:21 ` Andy Parkins [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=200611030821.54350.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).