From: Junio C Hamano <gitster@pobox.com>
To: Matthew Ogilvie <mmogilvi_git@miniinfo.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: have ls-files and ls-tree "see also" each other
Date: Mon, 04 Jun 2012 22:43:32 -0700 [thread overview]
Message-ID: <7vehpuqpob.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 1338873037-4343-1-git-send-email-mmogilvi_git@miniinfo.net
Matthew Ogilvie <mmogilvi_git@miniinfo.net> writes:
> Signed-off-by: Matthew Ogilvie <mmogilvi_git@miniinfo.net>
> ---
>
> I could have used these references when I was looking at git-ls-files
> documentation and trying to figure out how to make it list files
> from a specific commit like git-ls-tree.
I do not like this kind of patches in general. Where will it end?
"I wanted to know how to list objects recorded in a commit, and I
could have used a reference to git-ls-tree from git-commit, so here
is a patch to make them refer to each other"?
That kind of overfiew is what the tutorial (for concepts like the
index, tree objects, commit objects, etc.) and the list of commands
in git(1). Is there compelling reason other than "I didn't bother
to look, and it is likely other people wouldn't" to apply patches
like this?
next prev parent reply other threads:[~2012-06-05 5:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 5:10 [PATCH] Documentation: have ls-files and ls-tree "see also" each other Matthew Ogilvie
2012-06-05 5:43 ` Junio C Hamano [this message]
2012-06-05 6:29 ` Matthew Ogilvie
2012-06-05 15:03 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2012-05-14 3:28 Matthew Ogilvie
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=7vehpuqpob.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mmogilvi_git@miniinfo.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.