From: Fredrik Gustafsson <iveqy@iveqy.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org
Subject: Enhancements to git-protocoll
Date: Sat, 28 Jul 2012 23:41:16 +0200 [thread overview]
Message-ID: <20120728214116.GA3591@paksenarrion.iveqy.com> (raw)
Hi,
sometimes git communicates with something that's not git on the other
side (gitolite and github for example).
Sometimes the server wants to communicate directly to the git user.
git isn't really designed for this. gitolite solves this by do user
interaction on STDERR instead. The bad thing about this is that it can
only be one-direction communication, for example error messages.
If git would allow for the user to interact direct with the server, a
lot of cool and and userfriendly features could be developed.
For example:
gitolite has something called wild repos[1]. The management is
cumbersome and if you misspell when you clone a repo you might instead
create a new repo.
This could have been avoided with a simply:
"Do you want to create a new repo[Yn]"
To fix this, git protocol should have a command for printing input to
STDOUT and accepting input on STDIN which should be sent to the server.
And a command to switch back to orginal of course.
The server could then switch to user interaction, do that and then
switch back to normal operation.
Before eventually starting to implement this, I would know your
opinions. This feature would be wortless if it's not in the official git.
[1] http://sitaramc.github.com/gitolite/wild.html
--
Med vänliga hälsningar
Fredrik Gustafsson
tel: 0733-608274
e-post: iveqy@iveqy.com
next reply other threads:[~2012-07-28 21:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 21:41 Fredrik Gustafsson [this message]
2012-07-29 6:58 ` Enhancements to git-protocoll 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
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=20120728214116.GA3591@paksenarrion.iveqy.com \
--to=iveqy@iveqy.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).