git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stephen Boyd <bebarino@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] read-tree: migrate to parse-options
Date: Tue, 23 Jun 2009 22:08:06 -0700	[thread overview]
Message-ID: <7vws721ao9.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1245817672-25483-2-git-send-email-bebarino@gmail.com> (Stephen Boyd's message of "Tue\, 23 Jun 2009 21\:27\:52 -0700")

Stephen Boyd <bebarino@gmail.com> writes:

> Cleanup the documentation to explicitly state that --exclude-directory
> is only meaningful when used with -u. Also make the documentation more
> consistent with the usage message printed with read-tree --help-all.
>
> Signed-off-by: Stephen Boyd <bebarino@gmail.com>
> ---
>  Documentation/git-read-tree.txt |    5 +-
>  builtin-read-tree.c             |  220 +++++++++++++++++++++-----------------
>  2 files changed, 126 insertions(+), 99 deletions(-)

Sorry, but I have to ask: Why?

  reply	other threads:[~2009-06-24  5:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24  4:27 [PATCH 1/2] read-tree: convert unhelpful usage()'s to helpful die()'s Stephen Boyd
2009-06-24  4:27 ` [PATCH 2/2] read-tree: migrate to parse-options Stephen Boyd
2009-06-24  5:08   ` Junio C Hamano [this message]
2009-06-25  1:36     ` Stephen Boyd
2009-06-25  5:06   ` [PATCHv2 " Stephen Boyd
2009-06-25  6:55     ` Johannes Sixt
2009-06-26  3:15       ` Stephen Boyd
2009-06-26  5:14 ` [PATCHv3 1/2] read-tree: convert unhelpful usage()'s to helpful die()'s Stephen Boyd
2009-06-26  5:14   ` [PATCHv3 2/2] read-tree: migrate to parse-options Stephen Boyd
2009-06-26  5:29     ` Stephen Boyd
2009-06-26 17:23       ` Junio C Hamano
2009-06-27  2:00         ` Stephen Boyd

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vws721ao9.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=bebarino@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).