public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Levedahl <mdl123@verizon•net>
To: Junio C Hamano <junkio@cox•net>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Add git-unbundle - unpack objects and references for disconnected transfer
Date: Fri, 16 Feb 2007 18:21:30 -0500	[thread overview]
Message-ID: <45D63C7A.4050300@verizon.net> (raw)
In-Reply-To: <7vhctl50zc.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> Mark, how urgent do you want to have "bundle" in my tree?  As I
> understand it, this came out of your working zip based
> implementation your group already use, so I am suspecting that
> you do not have urgent need to have a different one in git.git
> in a half-baked shape.
>   
I can get my work done today with what I have. However, I really believe 
bundle is a good addition to git, and I don't want to maintain an 
out-of-tree patch to git to add this capability.
> Wouldn't it be nice if you can treat a bundle as just a
> different kind of git URL that you can "git fetch"?
>
> 	$ git fetch file.bdl 'refs/heads/*:refs/heads/*'
>   
yes
>
> Then git-ls-remote can be taught about a bundle file and use the
> 'git bundle --list-heads'.  Also, with something like this in
> your config:
>
> 	[remote "bundle"]
>         	url = /home/me/tmp/file.bdl
>                 fetch = refs/heads/*:refs/remotes/origin/*
>
> You can first sneakernet the bundle file to ~/tmp/file.bdl and
> then these commands:
>
> 	$ git ls-remote bundle
>         $ git fetch bundle
> 	$ git pull bundle
>
> would treat it as if it is talking with a remote side over the
> network.
>
> Hmm?
>
>   
As long as I can still do a "git fetch file.bdl" and without having to 
do the config stuff. I'm happy. Integrating this bundle with basic git 
approaches to things is obviously good. The frontend you outlined seems 
a trivial rearrangement of what I already have, but I'll let this 
discussion progress a bit further before I start doing that.

Mark

  reply	other threads:[~2007-02-16 23:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 12:53 Re: [PATCH] Add git-unbundle - unpack objects and references for disconnected transfer Mark Levedahl
2007-02-16 19:57 ` Junio C Hamano
2007-02-16 23:21   ` Mark Levedahl [this message]
2007-02-17  6:57     ` Junio C Hamano
2007-02-17 14:40       ` Mark Levedahl
2007-02-17 17:53         ` Junio C Hamano
2007-02-17 14:50   ` Mark Levedahl
2007-02-17 18:41     ` Junio C Hamano
2007-02-18 17:27       ` [PATCH] Add git-bundle: move objects and references by archive Mark Levedahl
2007-02-18 22:47         ` Mark Levedahl
2007-02-16 21:58 ` [PATCH] Add git-unbundle - unpack objects and references for disconnected transfer Mark Levedahl
2007-02-16 22:51   ` Johannes Schindelin
  -- strict thread matches above, loose matches on Subject: below --
2007-02-16  0:19 Respun - Scripts to use bundles to move data between repos Mark Levedahl
2007-02-16  0:19 ` [PATCH] Add git-bundle - pack objects and references for disconnected transfer Mark Levedahl
2007-02-16  0:19   ` [PATCH] Add git-unbundle - unpack " Mark Levedahl
2007-02-16  2:24     ` Junio C Hamano
2007-02-16  2:40       ` Linus Torvalds
2007-02-16  6:38         ` Mark Levedahl
2007-02-16  6:48           ` Shawn O. Pearce
2007-02-16  7:31             ` Junio C Hamano
2007-02-16  7:45               ` Shawn O. Pearce
2007-02-16  6:22       ` Mark Levedahl
2007-02-16  7:24         ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45D63C7A.4050300@verizon.net \
    --to=mdl123@verizon$(echo .)net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=junkio@cox$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox