* Paul Wise [Tue, 03 Mar 2009 11:30:13 +0900]:
> On Tue, Mar 3, 2009 at 1:37 AM, Adeodato Simó <d...@net.com.org.es> wrote:
> > 3. Git
> > ======
> > Git has shallow clones, created with the --depth option for git-clone.
> > This cut-offs the history of the project past a certain point, but the
> > result is lacking: mainly, you cannot push your changes back. (You can
> > do local commits however, and you can create patches for this in the
> > normal Git workflow.)
> This is wrong, you most certainly *can* push from a shallow clone to a
> full clone. I think you cannot (yet) push to a shallow clone though
> (haven't tried it myself).
Thanks for pointing that out: I stand corrected, it seems to work
indeed. (Which is awesome, and makes Git's standing on this comparison
much better IMHO.)
I was guiding myself from the documentation, not having used shallow
clones myself. From git-clone(1):
A shallow repository has a number of limitations (you cannot clone
or fetch from it, nor push from nor into it) [...]
^^^^^^^^^^^^^
Can you confirm whether my reading of the underlined part was correct in
assuming it meant you couldn't push from a shallow clone to a full clone?
I'll mail upstream about this.
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
Any life, no matter how long and complex it may be, is made up of a
single moment: the moment in which a man finds out, once and for all,
who he is.
-- Jorge Luis Borges
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
