From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Stefan Beller <sbeller@google.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>,
Dan Wang <dwwang@google.com>
Subject: Re: [PATCH 1/4] push options: {pre,post}-receive hook learns about push options
Date: Fri, 01 Jul 2016 12:25:39 -0700 [thread overview]
Message-ID: <xmqqr3bdxirw.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160701181102.GA16695@sigill.intra.peff.net> (Jeff King's message of "Fri, 1 Jul 2016 14:11:02 -0400")
Jeff King <peff@peff.net> writes:
> Compare to:
>
> if test "$GIT_PUSH_VAR_force" = true
> ...
OK. As this is a new feature, I guess it is not too bad if we tell
users that they cannot have duplicate keys in their <key,val> data
they ask Git to transport. They can do the key1=val1 key2=val2
numbering themselves if that is really needed.
next prev parent reply other threads:[~2016-07-01 19:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 0:59 [RFC PATCHv1 0/4] Push options in C Git Stefan Beller
2016-06-30 0:59 ` [PATCH 1/4] push options: {pre,post}-receive hook learns about push options Stefan Beller
2016-07-01 7:14 ` Jeff King
2016-07-01 17:20 ` Stefan Beller
2016-07-01 17:59 ` Jeff King
2016-07-01 18:03 ` Junio C Hamano
2016-07-01 18:11 ` Jeff King
2016-07-01 19:25 ` Junio C Hamano [this message]
2016-07-01 19:31 ` Stefan Beller
2016-07-01 19:39 ` Jeff King
2016-07-01 19:50 ` Stefan Beller
2016-07-01 18:40 ` Stefan Beller
2016-06-30 0:59 ` [PATCH 2/4] receive-pack: implement advertising and receiving " Stefan Beller
2016-07-01 17:11 ` Junio C Hamano
2016-07-01 17:24 ` Stefan Beller
2016-06-30 0:59 ` [PATCH 3/4] push: accept " Stefan Beller
2016-06-30 0:59 ` [PATCH 4/4] add a test for " Stefan Beller
2016-07-01 7:09 ` [RFC PATCHv1 0/4] Push options in C Git Jeff King
2016-07-01 17:07 ` Stefan Beller
2016-07-01 17:55 ` Jeff King
2016-07-01 18:25 ` Stefan Beller
2016-07-01 20:01 ` Jeff King
2016-07-07 1:12 [PATCHv3 " Stefan Beller
2016-07-07 1:12 ` [PATCH 1/4] push options: {pre,post}-receive hook learns about push options Stefan Beller
2016-07-07 20:20 ` Junio C Hamano
2016-07-07 21:50 ` Stefan Beller
2016-07-07 21:53 ` Junio C Hamano
2016-07-09 0:31 [PATCHv4 0/4] Push options Stefan Beller
2016-07-09 0:31 ` [PATCH 1/4] push options: {pre,post}-receive hook learns about push options Stefan Beller
2016-07-14 17:39 [PATCHv5 0/4] Push options Stefan Beller
2016-07-14 17:39 ` [PATCH 1/4] push options: {pre,post}-receive hook learns about push options Stefan Beller
2016-07-14 21:49 [PATCHv7 0/4] Push options Stefan Beller
2016-07-14 21:49 ` [PATCH 1/4] push options: {pre,post}-receive hook learns about push options Stefan Beller
2016-07-14 22:46 ` Jeff King
2016-07-14 22:51 ` Stefan Beller
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=xmqqr3bdxirw.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=dwwang@google.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sbeller@google.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.