On Wed, 17 Oct 2012, Junio C Hamano wrote:
> Mark Hills writes:
>
> >> > It looks like it might be easier (and less confusing to users) to derive
> >> > this attribute from the top-level .git directory?
> >>
> >> Hrm, clever ;-)
> >>
On Mon, 8 Oct 2012, Junio C Hamano wrote:
> Mark Hills writes:
>
> > We make extensive use of unix permissions and core.sharedRepository --
> > multiple developers push to the same repo.
> >
> > I have often wondered why core.sharedRepository is needed at all as
We make extensive use of unix permissions and core.sharedRepository --
multiple developers push to the same repo.
I have often wondered why core.sharedRepository is needed at all as a
separate configuration?
It looks like it might be easier (and less confusing to users) to derive
this attribut
On Mon, 3 Sep 2012, Sitaram Chamarty wrote:
> On Mon, Sep 3, 2012 at 5:17 PM, Konstantin Khomoutov
> wrote:
> > On Mon, 3 Sep 2012 11:21:43 +0100 (BST)
> > Mark Hills wrote:
>
> [snip]
>
> >> This is quite cumbersome; we have a large team of devs who use
On Mon, 3 Sep 2012, Ævar Arnfjörð Bjarmason wrote:
> On Mon, Sep 3, 2012 at 12:21 PM, Mark Hills wrote:
> > How do I clone a repo _to_ a new repo over SSH? I tried:
> >
> > cd xx
> > git clone --bare . gitserver:/scm/xx.git
> > git clone --bare . ssh://
How do I clone a repo _to_ a new repo over SSH? I tried:
cd xx
git clone --bare . gitserver:/scm/xx.git
git clone --bare . ssh://gitserver/scm/xx.git
This does not have the expected result, and instead a local path of the
given name is created (eg. a 'gitserver:' directory)
This seems to
6 matches
Mail list logo