Shawn Pearce spea...@spearce.org writes:
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.
Good point. The case that spawned this thread however
On Mon, Jul 30, 2012 at 11:58 AM, Junio C Hamano gits...@pobox.com wrote:
Heh. While I do not particularly consider auto-creation-upon-push a
useful thing to begin with (after all, once you created a
repository, you would want ways to manage it, setting up ACL for it
[side point] these
On Mon, Jul 30, 2012 at 11:58 AM, Junio C Hamano gits...@pobox.com wrote:
Shawn Pearce spea...@spearce.org writes:
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
Fredrik Gustafsson iv...@iveqy.com writes:
Sometimes the server wants to communicate directly to the git user.
...
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
On Sun, Jul 29, 2012 at 3:11 AM, Fredrik Gustafsson iv...@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
On Sun, Jul 29, 2012 at 04:07:13PM +0530, Sitaram Chamarty wrote:
On Sun, Jul 29, 2012 at 3:11 AM, Fredrik Gustafsson iv...@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
On Sat, Jul 28, 2012 at 11:58:09PM -0700, Junio C Hamano wrote:
Fredrik Gustafsson iv...@iveqy.com writes:
Sometimes the server wants to communicate directly to the git user.
...
For example:
gitolite has something called wild repos[1]. The management is
cumbersome and if you misspell
On Sun, Jul 29, 2012 at 7:43 PM, Fredrik Gustafsson iv...@iveqy.com wrote:
On Sun, Jul 29, 2012 at 04:07:13PM +0530, Sitaram Chamarty wrote:
On Sun, Jul 29, 2012 at 3:11 AM, Fredrik Gustafsson iv...@iveqy.com wrote:
Hi,
sometimes git communicates with something that's not git on the other
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
On Sun, Jul 29, 2012 at 8:35 PM, Fredrik Gustafsson iv...@iveqy.com wrote:
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
On Sun, Jul 29, 2012 at 08:45:39PM +0530, Sitaram Chamarty wrote:
I think you misunderstood how gitolite works. Gitolite does not have
*any* user interaction other than sending some extra messages back via
STDERR if you're using a normal git client to do normal git operations
On Sun, Jul 29, 2012 at 9:11 PM, Fredrik Gustafsson iv...@iveqy.com wrote:
On Sun, Jul 29, 2012 at 08:45:39PM +0530, Sitaram Chamarty wrote:
I think you misunderstood how gitolite works. Gitolite does not have
*any* user interaction other than sending some extra messages back via
STDERR if
Sitaram Chamarty sitar...@gmail.com writes:
Uggh, no. Client-git should only talk to server-git. It shouldn't be
talking first to some *other* program (in this case gitolite), and
then to to server-git. That doesn't sound sane to me.
You should wrap this whole thing around something else
Sorry I missed this thread earlier. I'll drop this if it's not something
that's wanted.
On Sun, Jul 29, 2012 at 01:51:34PM -0700, Junio C Hamano wrote:
Sitaram Chamarty sitar...@gmail.com writes:
Uggh, no. Client-git should only talk to server-git. It shouldn't be
talking first to some
Junio C Hamano gits...@pobox.com writes:
Sitaram Chamarty sitar...@gmail.com writes:
Uggh, no. Client-git should only talk to server-git. It shouldn't be
talking first to some *other* program (in this case gitolite), and
then to to server-git. That doesn't sound sane to me.
You should
On Mon, Jul 30, 2012 at 2:56 AM, Fredrik Gustafsson iv...@iveqy.com wrote:
Sorry I missed this thread earlier. I'll drop this if it's not something
that's wanted.
On Sun, Jul 29, 2012 at 01:51:34PM -0700, Junio C Hamano wrote:
Sitaram Chamarty sitar...@gmail.com writes:
Uggh, no.
On Mon, Jul 30, 2012 at 3:08 AM, Junio C Hamano gits...@pobox.com wrote:
Junio C Hamano gits...@pobox.com writes:
Sitaram Chamarty sitar...@gmail.com writes:
Uggh, no. Client-git should only talk to server-git. It shouldn't be
talking first to some *other* program (in this case gitolite),
Sitaram Chamarty sitar...@gmail.com writes:
As I may have said earlier, this interaction is far too site-specific
to be rolled into git itself.
How about a new hook instead? A pre-pack-protocol hook that acts as
if it was called by the remote user as a command, and if it exit's
with 0,
On Mon, Jul 30, 2012 at 6:51 AM, Shawn Pearce spea...@spearce.org wrote:
On Sun, Jul 29, 2012 at 6:04 PM, Sitaram Chamarty sitar...@gmail.com wrote:
Of course this will only work with ssh. None of what Fredrik has so
far suggested would possibly work on smart http without even more
hacks, I
On Mon, Jul 30, 2012 at 6:58 AM, Junio C Hamano gits...@pobox.com wrote:
Sitaram Chamarty sitar...@gmail.com writes:
As I may have said earlier, this interaction is far too site-specific
to be rolled into git itself.
How about a new hook instead? A pre-pack-protocol hook that acts as
if it
Shawn Pearce spea...@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
On Sun, Jul 29, 2012 at 7:38 PM, Junio C Hamano gits...@pobox.com wrote:
Shawn Pearce spea...@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
22 matches
Mail list logo
