git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [WIP PATCH] Add 'git fast-export', the sister of 'git fast-import'
Date: Fri, 23 Nov 2007 14:31:18 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711231428350.27959@racer.site> (raw)
In-Reply-To: <fcaeb9bf0711230431x1b0432f6uc9472b2f67514463@mail.gmail.com>

Hi,

On Fri, 23 Nov 2007, Nguyen Thai Ngoc Duy wrote:

> On Nov 21, 2007 10:40 AM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
> >
> > [WIP: this does not handle tags yet, and it lacks a test script
> >  as well as documentation.]
> >
> > This program dumps (parts of) a git repository in the format that
> > fast-import understands.
> >
> > For clarity's sake, it does not use the 'inline' method of specifying
> > blobs in the commits, but builds the blobs before building the commits.B
> >
> > ---
> >         I am way too tired now to continue, but maybe someone else wants
> >         to pick up the ball.
> 
> Well, I would better be back on setup_git_directory() than picking up
> the ball.

Concur.

> I have a suggestion though. git-fast-export and git-fast-import should 
> support bundle.

I think this is not what fast-export and fast-import are about.  They use 
an easy to generate, and easy to edit, format.

Bundles are optimised transport mechanisms for sneaker net.  They are not 
to be meant to be easy to edit, but as small as possible.

> Bundle is very handy for transferring a bunch of commits, but it does 
> not (cannot?) hold tags and branches.

But they can!  Nothing prevents you from calling

	git bundle create a1.bundle refs/tags/v1.0.0 refs/heads/next

(At least this is the idea, haven't tested yet).

Ciao,
Dscho

  reply	other threads:[~2007-11-23 14:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21  3:40 [WIP PATCH] Add 'git fast-export', the sister of 'git fast-import' Johannes Schindelin
2007-11-21  7:44 ` Johannes Sixt
2007-11-21  7:47   ` Shawn O. Pearce
2007-11-21 14:01   ` Johannes Schindelin
2007-11-21 15:09     ` Andreas Ericsson
2007-11-21 15:47       ` Johannes Schindelin
2007-11-21 15:53         ` Andreas Ericsson
2007-11-21 12:43 ` Geert Bosch
2007-11-21 14:42   ` Johannes Schindelin
2007-11-23  0:27 ` Han-Wen Nienhuys
2007-11-23  1:01   ` Johannes Schindelin
2007-11-23  1:23     ` Han-Wen Nienhuys
2007-11-23  2:11       ` Johannes Schindelin
2007-11-23 20:59         ` Shawn O. Pearce
2007-11-25 17:00           ` Karl Hasselström
2007-11-26 16:48             ` Johannes Schindelin
2007-11-27 10:16               ` Karl Hasselström
2007-11-27 11:25                 ` Johannes Schindelin
2007-11-27 14:51                   ` Karl Hasselström
2007-11-27 15:10                     ` Johannes Schindelin
2007-11-26 16:47           ` Johannes Schindelin
2007-11-23 12:31 ` Nguyen Thai Ngoc Duy
2007-11-23 14:31   ` Johannes Schindelin [this message]
2007-11-23 20:56     ` Shawn O. Pearce
2007-11-24 14:08     ` Nguyen Thai Ngoc Duy
2007-11-27 12:16       ` Johannes Schindelin
2007-11-27 14:17         ` Nguyen Thai Ngoc Duy

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.0711231428350.27959@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=pclouds@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).