Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Chí-Thanh Christopher Nguyễn <chithanh@g.o>
Subject: Re: Portage Git migration - clean cut or git-cvsserver
Date: Wed, 23 May 2012 19:38:16 +0200
Alexey Shvetsov schrieb:
>> Shallow clones are also read-only last I checked.
> 
> That isnt true =) you can commit from shallow clone  if and only if
> original repo doesnt have a branching and merging points before and
> after shallow clone point respectively

There can also be breakage when someone reverts a commit that it is not
part of your shallow clone's history, and then you pull.


Best regards,
Chí-Thanh Christopher Nguyễn


Replies:
Re: Portage Git migration - clean cut or git-cvsserver
-- Arun Raghavan
Re: Portage Git migration - clean cut or git-cvsserver
-- Rafael Goncalves Martins
References:
Portage Git migration - clean cut or git-cvsserver
-- Michael Weber
Re: Portage Git migration - clean cut or git-cvsserver
-- Alexey Shvetsov
Re: Portage Git migration - clean cut or git-cvsserver
-- Robin H. Johnson
Re: Portage Git migration - clean cut or git-cvsserver
-- Alexey Shvetsov
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Portage Git migration - clean cut or git-cvsserver
Next by thread:
Re: Portage Git migration - clean cut or git-cvsserver
Previous by date:
Re: Portage Git migration - clean cut or git-cvsserver
Next by date:
Re: Re: Remove eclass/ChangeLog


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.