From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: Fredrik Gustafsson <iveqy@iveqy.com>,
gitster@pobox.com, git@vger.kernel.org
Subject: Re: Enhancements to git-protocoll
Date: Sun, 29 Jul 2012 16:13:54 +0200 [thread overview]
Message-ID: <20120729141354.GA16223@paksenarrion.iveqy.com> (raw)
In-Reply-To: <CAMK1S_i7WjrZ=L_LVoTQriW8kKMPd+ABrgowpFCY3ks43E6K7A@mail.gmail.com>
On Sun, Jul 29, 2012 at 04:07:13PM +0530, Sitaram Chamarty wrote:
> On Sun, Jul 29, 2012 at 3:11 AM, Fredrik Gustafsson <iveqy@iveqy.com> wrote:
> > 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.
>
> For the record, although it cannot do the yes/no part, if you want to
> disable auto-creation on a fetch/clone (read operation) it's trivial
> to add a "PRE_CREATE" trigger to do that.
Thanks, however I think auto-creation is a great feature for some cases
and I think there can be even more useable functions if we could get
user interaction.
--
Med vänliga hälsningar
Fredrik Gustafsson
tel: 0733-608274
e-post: iveqy@iveqy.com
next prev parent reply other threads:[~2012-07-29 14:13 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
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 [this message]
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=20120729141354.GA16223@paksenarrion.iveqy.com \
--to=iveqy@iveqy.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sitaramc@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;
as well as URLs for NNTP newsgroup(s).