I do: `git clone --depth 0 ./repo1/ repo2` I expected that "git log" in repo2 wouldn't show any revisions, but it does.
I'm using 1.6.5.3.171.ge36e.dirty (small unrelated modification).
Am I doing something incorrectly?
regards, dan carpenter
Björn SteinbrinkRe: does clone --depth work?
On 2009.11.29 18:03:52 +0200, Dan Carpenter wrote:
Show 6 quoted lines
> I do: `git clone --depth 0 ./repo1/ repo2` I expected that > "git log" in repo2 wouldn't show any revisions, but it does. > > I'm using 1.6.5.3.171.ge36e.dirty (small unrelated modification). > > Am I doing something incorrectly?
Two problems: a) IIRC depth = 0 is like not specifying depth at all b) When using plain paths, clone optimizes the process by just doing a copy, that doesn't apply the depth setting at all
git clone --depth=1 file://$PWD/repo1 repo2
That should work. Of course you still got some commits, so "git log" will show them. You just don't get all of them, but only to a certain depth.
Björn
Re: does clone --depth work?
On Sun, Nov 29, 2009 at 05:32:42PM +0100, Björn Steinbrink wrote:
Show 15 quoted lines
> On 2009.11.29 18:03:52 +0200, Dan Carpenter wrote: > > I do: `git clone --depth 0 ./repo1/ repo2` I expected that > > "git log" in repo2 wouldn't show any revisions, but it does. > > > > I'm using 1.6.5.3.171.ge36e.dirty (small unrelated modification). > > > > Am I doing something incorrectly? > > Two problems: > a) IIRC depth = 0 is like not specifying depth at all > b) When using plain paths, clone optimizes the process by just doing a > copy, that doesn't apply the depth setting at all > > git clone --depth=1 file://$PWD/repo1 repo2 >
Awesome. That does work.
thanks, dan
Show 5 quoted lines
> That should work. Of course you still got some commits, so "git log" > will show them. You just don't get all of them, but only to a certain > depth. > > Björn