# Re: Shallow clone \[Was Re: What's in git.git \]

- From: Aneesh Kumar K.V \<hidden\>
- Date: 2016-08-11 20:06:19 
- List: git
- Page: https://ratatoskr.run/git/2016/08/7690616
- Thread: https://ratatoskr.run/git/2016/08/7687999/t.md

```text
Aneesh Kumar K.V wrote:
> David Lang wrote:
>> On Tue, 7 Nov 2006, Junio C Hamano wrote:
>>
>>> [pu]
>>>
>>>  Johannes's shallow clone work now should rebase cleanly on top
>>>  of 'master' although I haven't done so yet.  As he said
>>>  himself the series is waiting for people who have needs for
>>>  such a feature to raise hands.
>>
>> I haven't been watching this recently, but if this is what I understand it to be (the ability to get a partial repository from upstream and work normally from there with the result of data-mineing tools sometimes reporting 'that's part of the truncated history' if they hit the cutoff) consider my hand raised.
>>
>> there are a number of cases where I would be interested in following a project as it moves forwards, but do not have the need to have the full history (even with the good compression that a git pack provides, it's still a significant amount of disk space and download time for large projects)
>>
>
> I am trying to test this feature. Is there a documentation .git/shallow some where. Atleast what those entries
> mean ? I know in the mail johannes mentioned only core git will touch this file. But it should be ok to be descriptive like other files. (FETCH_HEAD)


How about this

-aneesh
```

## Attachments

- [repository-layout.txt.diff](https://ratatoskr.run/git/2016/08/7690616/attachment/0) (text/x-patch, 537 bytes)