git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 17:05:50 +0200	[thread overview]
Message-ID: <20120729150550.GA17679@paksenarrion.iveqy.com> (raw)
In-Reply-To: <CAMK1S_iFqQvU+USYf+wcsLFS1QtsytLnPfEhjcAVZa9Vwj8d1w@mail.gmail.com>

On Sun, Jul 29, 2012 at 07:55:36PM +0530, Sitaram Chamarty wrote:
> > 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.
> 
> For the record, I don't think I agree.  There's a place to create a
> human-conversation, and there's a place not to.
> 
> If you want a dialog with the server, there should be *other* commands
> that do that, instead of overloading git's own protocol.
> 
> Since you mentioned gitolite, consider copying the fork command
> (src/commands/fork) and munging the code into an explicit wild repo
> create.

I appriciate that you clearified you oppinion. Please excuse me if it
sounded as I in any way speaked for gitolite. I use gitolite as an
example becuase the target application in this case is unknown to most
people (think gitolite with db-backend for user permissions).

It's a valid design oppinion to not mix git protocoll with anything
else. But gitolite already does that. Gitolite already have user
interaction mixed with git interaction. Do you say to me that gitolite
is broken and should not do user interaction over git-commands? Then why
does wild repos exists and why does gitolite error messages exists?

We're already down that road, why not do it better?

-- 
Med vänliga hälsningar
Fredrik Gustafsson

tel: 0733-608274
e-post: iveqy@iveqy.com

  reply	other threads:[~2012-07-29 15:05 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
2012-07-29 14:25     ` Sitaram Chamarty
2012-07-29 15:05       ` Fredrik Gustafsson [this message]
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=20120729150550.GA17679@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).