Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] ls-remote: a lone "-h" is asking for help
Date: Fri, 16 Sep 2011 13:53:48 -0700	[thread overview]
Message-ID: <7vpqj0dx9f.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAGdFq_jc4YDaD+NL6_+buCrOt2yAK+-_MDOJQU5qnS13P65CzQ@mail.gmail.com> (Sverre Rabbelier's message of "Fri, 16 Sep 2011 22:34:24 +0200")

Sverre Rabbelier <srabbelier@gmail.com> writes:

> ... Should we have some way to queue patches like
> this, or would someone have to resend after the appropriate release?

For this particular case, I do not think it is worth _my_ time to keep
maintaining that patch.

It is understandable that a new person will be hurt if

	$ git ls-remote -h

does not give a short-help message and instead try to contact and show the
origin repository which may not even exist, and that is why I sent a fix.

But would anybody gets hurt if

	$ git ls-remote -h origin
        $ git ls-remote -h git://git.kernel.org/pub/git/git.git

kept working as they do today, given that we do not advertise -h as
a synonym in "git ls-remote -h" output?

That is why I said "I am not opposed to", and not "I'd volunteer to do
that". It's not worth my time, but since you brought it up, you may care
more about it.

      reply	other threads:[~2011-09-16 20:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 18:14 [PATCH] ls-remote: a lone "-h" is asking for help Junio C Hamano
2011-09-16 19:09 ` Sverre Rabbelier
2011-09-16 19:35   ` Junio C Hamano
2011-09-16 19:44     ` Sverre Rabbelier
2011-09-16 20:31       ` Junio C Hamano
2011-09-16 20:34         ` Sverre Rabbelier
2011-09-16 20:53           ` Junio C Hamano [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=7vpqj0dx9f.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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