From: Junio C Hamano <gitster@pobox.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: Sitaram Chamarty <sitaramc@gmail.com>,
Fredrik Gustafsson <iveqy@iveqy.com>,
git@vger.kernel.org
Subject: Re: Enhancements to git-protocoll
Date: Sun, 29 Jul 2012 19:38:58 -0700 [thread overview]
Message-ID: <7vehnut1kt.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAJo=hJsgMz-=pdG=HB3KtTE7g6Gvu9mr56dg2+V3WUST+rpAQg@mail.gmail.com> (Shawn Pearce's message of "Sun, 29 Jul 2012 18:21:20 -0700")
Shawn Pearce <spearce@spearce.org> writes:
> We sort of want this in Gerrit Code Review to pass reviewer names on
> the command line of git push, making it easier for users to upload a
> code review. The idea is similar to what happens with gcc accepting
> linker flags that are just passed onto the linker.
For reviewer names, authentication cookies and things of that nature
where the extra pieces of information affect the outcome in a way
that does not have to change how the underlying protocol exchange
works, such an additional one-way channel from the pusher to pushee
to carry auxiliary information would be sufficient. The server may
decide to accept otherwise forbidden, or reject otherwise permitted,
push based on the extra information given, for example, and that is
an example of an enhancement that does not have to change how the
underlying protocol exchange works.
The way to expose the extra information parsed by Git to the server
side could be made into calling out to hooks, and at that point,
gitolite would not even have to know about the pack protocol.
Perhaps the interface to such a hook may be "hook can tell Git to
abort the communication by exiting non-zero, after giving a message
to its standard output".
It is a separate matter if it makes sense to add another channel
that goes the other way on demand (i.e. taking the end-user
response from the pusher and giving it to the pushee, and then
allowing the pushee change its behaviour in a way more than just
simply aborting the connection but performing a useful alternative
operation)---I doubt it is.
next prev parent reply other threads:[~2012-07-30 2:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 21:41 Enhancements to git-protocoll Fredrik Gustafsson
2012-07-29 6:58 ` Junio C Hamano
2012-07-29 14:24 ` Fredrik Gustafsson
2012-07-29 14:39 ` Sitaram Chamarty
2012-07-29 20:51 ` Junio C Hamano
2012-07-29 21:26 ` Fredrik Gustafsson
2012-07-30 0:37 ` Sitaram Chamarty
2012-07-29 21:38 ` Junio C Hamano
2012-07-30 1:04 ` Sitaram Chamarty
2012-07-30 1:21 ` Shawn Pearce
2012-07-30 1:33 ` Sitaram Chamarty
2012-07-30 2:38 ` Junio C Hamano [this message]
2012-07-30 5:20 ` Shawn Pearce
2012-07-30 6:28 ` Junio C Hamano
2012-07-30 8:12 ` Sitaram Chamarty
2012-07-30 8:31 ` Sitaram Chamarty
2012-07-30 1:28 ` Junio C Hamano
2012-07-30 1:45 ` Sitaram Chamarty
2012-07-29 10:37 ` Sitaram Chamarty
2012-07-29 14:13 ` Fredrik Gustafsson
2012-07-29 14:25 ` Sitaram Chamarty
2012-07-29 15:05 ` Fredrik Gustafsson
2012-07-29 15:15 ` Sitaram Chamarty
2012-07-29 15:41 ` Fredrik Gustafsson
2012-07-29 18:22 ` Sitaram Chamarty
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=7vehnut1kt.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.com \
--cc=sitaramc@gmail.com \
--cc=spearce@spearce.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.
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).