git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Sverre Rabbelier" <srabbelier@gmail.com>,
	"Ævar Arnfjörð" <avarab@gmail.com>,
	"Artur Skawina" <art.08.09@gmail.com>,
	"Git List" <git@vger.kernel.org>
Subject: Re: Determining commit reachability
Date: Tue, 7 Sep 2010 23:07:07 +1000	[thread overview]
Message-ID: <AANLkTimzSV-M_ed8-vK+P_3-QpC3THdEpMQZbuM1Q-Sp@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimhucSrdQ6GKEDkWXuZkF+oCJbGkP_ZxgR3FdVg@mail.gmail.com>

On Tue, Sep 7, 2010 at 11:04 PM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
> On Tue, Sep 7, 2010 at 9:38 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> Somehow people wanted to see an option with a longer name, but by that
>> time my fingers were well trained, so I kept "--with" but didn't bother
>> advertising duplicated options.
>
> But do you object a document patch for that option? I ask because I
> found another undocumented option, --clear-resolve-undo in
> update-index and was wondering if it's worth a patch.

Hmm.. just saw Jonathan's patch. I guess I just go ahead and make a patch then.
-- 
Duy

      reply	other threads:[~2010-09-07 13:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-05 20:34 Determining commit reachability Artur Skawina
2010-09-06  3:17 ` Jeff King
2010-09-06  5:04   ` Artur Skawina
2010-09-06  6:47 ` Junio C Hamano
2010-09-06 20:45   ` Sverre Rabbelier
2010-09-06 20:53     ` Ævar Arnfjörð Bjarmason
2010-09-06 21:05       ` Sverre Rabbelier
2010-09-06 23:38         ` Junio C Hamano
2010-09-07  5:52           ` [PATCH] Documentation: explain "git branch --with" Jonathan Nieder
2010-09-07 10:51             ` Ævar Arnfjörð Bjarmason
2010-09-09 22:45             ` Junio C Hamano
2010-09-07 13:04           ` Determining commit reachability Nguyen Thai Ngoc Duy
2010-09-07 13:07             ` Nguyen Thai Ngoc Duy [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=AANLkTimzSV-M_ed8-vK+P_3-QpC3THdEpMQZbuM1Q-Sp@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=art.08.09@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=srabbelier@gmail.com \
    /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).