Re: Tracking a repository for content instead of history
On 12/12/06, Andy Parkins <andyparkins@gmail.com> wrote:
Show 23 quoted lines
> I suppose so; but I was thinking more an automated way of getting the data
> that is supplied for the kernel anyway. So:
>
> base-v1.0.0.tar.gz
> patch-v1.0.1.gz
> patch-v1.0.2.gz
> etc
>
> Each patch is obviously smaller than "base". Git could easily make the
> patches, and each of those patches could be fed by hand into a repository
> with git-apply. It doesn't seem like something that would require support on
> the other side, because it isn't so much a shallow clone (which /would/
> preserve history, making it available if wanted); it is pulling just, say,
> tagged commits out of an existing repository.
>
> Given a list of tags it is almost:
>
> git-archive <get me base>
> ssh remote git-diff v1.0.0..v1.0.1 | git-apply; git commit
> ssh remote git-diff v1.0.1..v1.0.2 | git-apply; git commit
>
> If that makes sense? Obviously though it would be possible to use git rather
> than ssh to do this.
Hm.. I'm no git:// expert. But is it possible doing as follow?
1. git-archive <base>
2. reconstruct commit, blobs and trees from the archive
3. tell git server that you have one commit, you need another commit
(maybe heads only, i'm not sure here)
4. get the pack from git server, create new commit and a diff
Nguyen Thai Ngoc Duy <pclouds@gmail.com>