[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-scm-interest
Subject: Re: [Kde-scm-interest] Gitolite server-side clones and personal
From: Thomas Zander <zander () kde ! org>
Date: 2010-06-17 13:48:10
Message-ID: 201006171548.10798.zander () kde ! org
[Download RAW message or body]
On Thursday 17. June 2010 12.46.48 Jeff Mitchell wrote:
> On 06/16/2010 08:42 AM, Thiago Macieira wrote:
> > Em Quarta-feira 16 Junho 2010, ās 14:17:58, Johannes Sixt escreveu:
> >> But you can place such branches in a new ref namespace on the server:
> >> refs/personal/myname/mybranch (as opposed to refs/heads/personal/....).
> >> Such refs are hidden from regular clone/fetch/pull, but you can still
> >> access them using
> >>
> >> git pull origin personal/myname/mybranch
> >>
> >> Users who regularly exchange topics in this way can write them down in
> >> the
> >>
> >> config file:
> >> fetch = +refs/personal/hausmann/*:refs/remotes/origin/hausmann/*
> >>
> >> To push such a branch for the first time is not straight-forward, though:
> >> git push origin my-topic:refs/personal/hausmann/my-topic
> >>
> >> and I don't know whether cgit and redmine can show or work with such
> >> refs, and any cleanup is still not automatic ;)
> >
> > That's no different than a separate repo.
> >
> > The advantage is automatic sharing of objects in gc.
>
> Not quite true -- the other advantage is that, if we have the clone on
> the cgit/redmine server pulling all personal branches, it can show those
> personal branches in the code browsers.
Which is also no difference from a separate repo by having your clone have
multiple remotes.
--
Thomas Zander
_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic