[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: git hang-ups
From: |
Mark Polesky |
Subject: |
Re: git hang-ups |
Date: |
Fri, 7 Aug 2009 20:39:16 -0700 (PDT) |
Patrick McCarty wrote:
> I've just tested git's shallow cloning feature. It's pretty neat.
> :-)
>
> From what I can see, shallow clones would be okay for *casual*
> contributors that are only sending patches based on the tip of master.
>
> However, since git history is limited to the depth of the clone, then
> shallow clones would not permit a developer to revert a commit from,
> say, three weeks ago.
>
> In other words, I think both the "git clone" and "git clone --depth"
> methods should be included in the CG.
To me, it seems that a developer should be able to just stick to
shallow clones for everyday use. I assume that one could simply
increase the depth of the clone when needed. Is that true? I've never
needed to revert a three-week old commit, but if I needed to, I
figure I would just do another clone with a greater depth.
Does it work that way?
- Mark
- Re: git hang-ups, (continued)
- Re: git hang-ups, Mark Polesky, 2009/08/03
- Re: git hang-ups, Graham Percival, 2009/08/03
- Re: git hang-ups, Mark Polesky, 2009/08/04
- Re: git hang-ups, Graham Percival, 2009/08/04
- Re: git hang-ups, Trevor Daniels, 2009/08/04
- Re: git hang-ups, Mark Polesky, 2009/08/04
- Re: git hang-ups, Patrick McCarty, 2009/08/07
- Re: git hang-ups,
Mark Polesky <=
- Re: git hang-ups, Patrick McCarty, 2009/08/07
- Re: git hang-ups, John Mandereau, 2009/08/08
- Re: git hang-ups, Trevor Daniels, 2009/08/08
Re: git hang-ups, Trevor Daniels, 2009/08/03