All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Keller\, Jacob E" <jacob.e.keller@intel.com>
Cc: "sunshine\@sunshineco.com" <sunshine@sunshineco.com>,
	"git\@vger.kernel.org" <git@vger.kernel.org>,
	"barkalow\@iabervon.iabervon.org"
	<barkalow@iabervon.iabervon.org>,
	"jacob.keller\@gmail.com" <jacob.keller@gmail.com>
Subject: Re: [PATCH 2/2] refs: loosen restriction on wildcard "*" refspecs
Date: Thu, 23 Jul 2015 17:51:37 -0700	[thread overview]
Message-ID: <xmqqlhe6nzs6.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1437698706.22096.5.camel@intel.com> (Jacob E. Keller's message of "Fri, 24 Jul 2015 00:45:06 +0000")

"Keller, Jacob E" <jacob.e.keller@intel.com> writes:

>> > s/hangled/handled/
>> > ...
>> 
>> Thanks; here is what I queued yesterday.
>> 
>
> Woah. I bow to your imperative commit message abilities. The new commit
> message is very nicely worded.

Heh, imperative is secondary. I just wanted to straighten out the
use of "refs" and "refspecs" there.

Thanks for a patch that was cleanly done.

      reply	other threads:[~2015-07-24  0:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 21:05 [PATCH v5 0/2] refs: cleanup and new behavior Jacob Keller
2015-07-22 21:05 ` [PATCH 1/2] refs: cleanup comments regarding check_refname_component Jacob Keller
2015-07-22 21:05 ` [PATCH 2/2] refs: loosen restriction on wildcard "*" refspecs Jacob Keller
2015-07-22 22:04   ` Junio C Hamano
2015-07-22 23:24     ` Jacob Keller
2015-07-23 16:44       ` Junio C Hamano
2015-07-23 16:51         ` Jacob Keller
2015-07-23 17:13         ` Junio C Hamano
2015-07-23 17:18           ` Jacob Keller
2015-07-23 22:00   ` Eric Sunshine
2015-07-23 22:12     ` Junio C Hamano
2015-07-24  0:45       ` Keller, Jacob E
2015-07-24  0:51         ` 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=xmqqlhe6nzs6.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jacob.keller@gmail.com \
    --cc=sunshine@sunshineco.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 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.