git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Nagy Balázs" <js@iksz.hu>
Cc: Jakub Narebski <jnareb@gmail.com>,
	Bruno Cesar Ribas <ribas@c3sl.ufpr.br>,
	git@vger.kernel.org
Subject: Re: [PATCH] Added sub get_owner_file which checks if there's a file with project owner name
Date: Fri, 1 Feb 2008 20:10:39 +0100	[thread overview]
Message-ID: <200802012010.40739.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <47A3449E.6070102@iksz.hu>

fredagen den 1 februari 2008 skrev Nagy Balázs:
> Well, I came from ClearCase world, were registry service holds all 
> vob/view (repo) stuff.  What if we implement more or less the same 
> here?  I mean if you have a lot of public git repos, or at least common 
> for a couple of people, we could store all the fundamental data (local 
> storage path, share URL) of a group of repos in a single database.  We 
> could call them depots.  Moreover, we could use this as the source of 
> git clone, God forbid, even remotely (some kind of git config 
> depot.url=https://user:pass@git.example.org/depot.cgi/depotname).  I 
> could continue but I'm afraid I'll run out of oxygen :)

I'll fill in: LDAP.

-- robin

      reply	other threads:[~2008-02-01 20:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29  3:36 [PATCH] Added sub get_owner_file which checks if there's a file with project owner name Bruno Ribas
2008-01-29 11:26 ` Jakub Narebski
2008-01-29 14:25   ` Bruno Cesar Ribas
2008-01-29 15:28     ` Jakub Narebski
2008-01-29 17:22       ` Bruno Cesar Ribas
2008-01-29 18:27         ` Jakub Narebski
2008-01-29 20:53       ` Nagy Balázs
2008-01-29 21:36         ` Jakub Narebski
2008-01-30 15:59           ` Nagy Balázs
2008-02-01 13:18             ` Jakub Narebski
2008-02-01 16:11               ` Nagy Balázs
2008-02-01 19:10                 ` Robin Rosenberg [this message]

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=200802012010.40739.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=js@iksz.hu \
    --cc=ribas@c3sl.ufpr.br \
    /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).