Re: [PATCH] Add git-unbundle - unpack objects and references for disconnected transfer
- From
Junio C Hamano <junkio@cox.net>
- Date
- Feb 17, 2007, 18:41 UTC
- Message-ID
- <7vejootynq.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <45D7161C.3050604@verizon.net>
Mark Levedahl <mdl123@verizon.net> writes:
Show 12 quoted lines
> Junio C Hamano wrote: >> I haven't thought things through, but I think something like this >> would be sufficient: >> >> # create a bundle. >> $ git bundle --create v1.5.0..maint master next >file.bdl >> >> > In this vein, would it make sense to let git-push be the front end to > create the bundle? I'm not sure git-push really contributes anything, > but the interface would then be consistent across all transports. Just > a thought.
I am not sure. For the "fetch" case, the UI will be exactly the same (URL and then refspecs), but we never say bottom commits for git-push. When you are creating a bundle, unless you are including everything, you want a way to say which bottom commits to be excluded from the resulting pack, so they are different. I had an impression bundle creation is similar to archive.