git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Santi Béjar" <sbejar@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Wishlist for a bundle-only transport mode
Date: Wed, 21 Nov 2007 15:59:51 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711211554370.27959@racer.site> (raw)
In-Reply-To: <8aa486160711210654p357ccd87i4809e0cda9471303@mail.gmail.com>

Hi,

On Wed, 21 Nov 2007, Santi B?jar wrote:

> 1) git-clone does not accept a bundle file, even if git-fetch does. I've 
> made a patch to use git-fetch in git-clone for this.

This, along with rewriting git-clone as a very thin wrapper over git-init, 
-remote and -fetch, is a really low hanging fruit.

Or maybe go the full nine yards and build it in.  Should be a breeze now, 
given parse_options() and run_command().

> 2) The bundles created with "git bundle" does not record the HEAD, they 
> resolve the symbolic name to a branch name.

It imitates ls-remote output.

> 3) I can "git fetch" a bundle but I cannot "git push" a bundle, so if I have:
> 
> [remote "bundle"]
>   url = /file/to/bundle
>   fetch = "+refs/heads/*:refs/remotes/bundle/*"
> 
> $ git push bundle
> 
> would create a bundle in /file/to/bundle with the same branches as a
> normal git push, but considering the remote branches as the local
> remotes/bundle/*

Does not seem to be too complicated to add it to transport.c IMHO.  
Something similar to rsync_transport_push().  And I'd definitely refuse to 
overwrite any existing file.

Ciao,
Dscho

  parent reply	other threads:[~2007-11-21 16:00 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 14:54 Wishlist for a bundle-only transport mode Santi Béjar
2007-11-21 15:04 ` Jakub Narebski
2007-11-21 15:24   ` Santi Béjar
2007-11-21 15:46   ` Johannes Schindelin
2007-11-21 16:52     ` Jakub Narebski
2007-11-21 16:59       ` Johannes Schindelin
2007-11-21 17:11         ` Jakub Narebski
2007-11-21 17:26           ` Johannes Schindelin
2007-11-21 17:52             ` Jakub Narebski
2007-11-22  9:42             ` Santi Béjar
2007-11-22 10:02               ` Junio C Hamano
2007-11-23  9:18                 ` Jakub Narebski
2007-11-23  9:31                   ` Junio C Hamano
2007-11-23 10:04                     ` Jakub Narebski
2007-11-23 10:13                     ` Santi Béjar
2007-11-23 12:18                       ` Johannes Schindelin
2007-11-23 15:06                       ` Junio C Hamano
2007-11-23 15:34                         ` Santi Béjar
2007-11-23 16:05                           ` Junio C Hamano
2007-11-23 16:39                             ` Santi Béjar
2007-11-24 19:15                               ` Junio C Hamano
2007-11-23 19:09                           ` Jakub Narebski
2007-11-21 15:59 ` Johannes Schindelin [this message]
2007-11-21 16:15   ` Santi Béjar
2007-11-21 16:36     ` Johannes Schindelin
2007-11-21 16:44       ` Santi Béjar
2007-11-21 16:53     ` [PATCH] bundle create: keep symbolic refs' names instead of resolving them Johannes Schindelin
2007-11-22 12:03       ` Johannes Schindelin
2007-11-22 12:24       ` [REPLACEMENT PATCH] " Johannes Schindelin
2007-11-21 16:23   ` Wishlist for a bundle-only transport mode Kristian Høgsberg
2007-11-21 17:07     ` Johannes Schindelin
2007-11-21 17:06 ` Jakub Narebski
2007-11-21 17:29   ` Johannes Schindelin

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=Pine.LNX.4.64.0711211554370.27959@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=sbejar@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).