"Kai Hendry" <hendry@aplixcorp.com> writes:

quoted text
> So I expected it to work like so:
>
> git clone git://git.webkit.org/WebKit.git
> git checkout -b test
>
> <Make a few small changes and commit>
>
> git-config remote.upload.url ssh://git.webvm.net/srv/git/webkit-test

A set of big questions is how that git.webvm.net/srv/git/webkit-test
repository was prepared, what its history look like and how it relates to
the history your repository has.  I presume that that is different from
the repository you are pushing from (which is "x61:aplix/test/WebKit"
repository), but other than that you did not give any details to guess
further.

quoted text
> x61:~/aplix/test/WebKit% git push --thin -v upload test

By the way, that --thin is an implementation detail and not meant for the
end user consumption.  I do not think it would matter in this case,
though.

quoted text
> Pushing to ssh://git.webvm.net/srv/git/webkit-test
> Counting objects: 371612, done.
> Compressing objects: 100% (67851/67851), done.
> Writing objects:  11% (43886/371612), 25.32 MiB | 88 KiB/
>
> However when uploading the branch it seems to upload _everything_
> which is far too big and impractical. Couldn't it just somehow
> reference the remote branch and just publish the patch of the "small
> changes"?

What you described is exactly what is supposed to be doing, but again as
we do not know how that git.webvm.net:/srv/gi/webkit-test/ repository was
prepared, we cannot tell.

But I have a theory:

    http://thread.gmane.org/gmane.comp.version-control.git/77643

and the latest code is still parked in 'pu' branch.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html