I consider 'git push' need further optimization.
Take kernel source code for example:
# Clone the kernel to A and B
$ git --version
git version 2.3.2
$ git clone --bare ../kernel/ A
$ git clone --bare ../kernel/ B
# Create the orphan commit and check
$ cd A
$ git branch test
Switched to a new
> Instead, the object transfer is optimized by comparing what commits
> each side has and sending trees and blobs that are reachable from
> the commits that the receiving side does not have.
The sender A sends all the commits that the receiver B does not have.
The commits contains trees and
I try to use 'git replace --graft' to work aroud this. Here's the process:
cd A
fetch ../B master:master_b
git replace --graft master_b master_a
# now master_b's parent is master_a
# do a filter-branch to make the stone solid
git filter-branch --tag-name-filter cat --
f space.
Yet it turns out I'm wrong. Since Repo A has been published, pushing branch of B
will double the repo size, which is impossible for the storage limit.
Any suggestions? Thanks in advance.
Best Regards,
Levin Du
--
To unsubscribe from this list: send the line "unsubscribe git" in
4 matches
Mail list logo
