git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sverre Rabbelier <srabbelier@gmail.com>
To: Matt McClure <mlm@aya.yale.edu>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	vcs-fast-import-devs@lists.launchpad.net, git@vger.kernel.org,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [Vcs-fast-import-devs] What's cooking in git.git (Oct 2009, #01;  Wed, 07)
Date: Sun, 11 Oct 2009 13:58:59 +0200	[thread overview]
Message-ID: <fabb9a1e0910110458x430dd67co330ba5f5bd550f9c@mail.gmail.com> (raw)
In-Reply-To: <e48c5e540910110440k33e3d0dcp6d8c1480b5848366@mail.gmail.com>

Heya,

On Sun, Oct 11, 2009 at 13:40, Matt McClure <mlm@aya.yale.edu> wrote:
> Who is the fast-output developer to say that only one fast-import tool
> should use his stream?

He knows that a foreign tool that does not heed his 'option git
stream-changing-option' will mis-parse the stream. For example the
Bazaar people were talking about adding some Bazaar-specific options
so facilitate bzr-bzr traffic, it would be impossible for a non-bzr
importer to properly understand the stream if they were to ignore the
bzr-specific options. So either options should only affect things that
do not change semantics (such as perhaps whether or not to be quiet,
whether to try and limit memory usage, etc), or it should be possible
to indicate that an option is changes semantic and cannot be ignored.

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2009-10-11 12:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08  6:33 What's cooking in git.git (Oct 2009, #01; Wed, 07) Junio C Hamano
2009-10-08  6:49 ` Johannes Schindelin
2009-10-08  6:49   ` Sverre Rabbelier
2009-10-08 17:39     ` Shawn O. Pearce
2009-10-08 17:58       ` Sverre Rabbelier
2009-10-11 11:40         ` [Vcs-fast-import-devs] " Matt McClure
2009-10-11 11:58           ` Sverre Rabbelier [this message]
2009-10-28 22:08         ` Sverre Rabbelier
2009-10-28 23:19           ` [Vcs-fast-import-devs] " Ian Clatworthy
2009-10-29 10:54           ` Johannes Schindelin
2009-10-30  3:50         ` [Vcs-fast-import-devs] " Ian Clatworthy
2009-10-30 12:41           ` Sverre Rabbelier
2009-10-08  6:58 ` Marius Storm-Olsen
2009-10-08 18:15   ` Erik Faye-Lund
2009-10-09  6:47     ` Junio C Hamano
2009-10-09  1:38 ` Jakub Narebski
2009-10-09  6:46   ` 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=fabb9a1e0910110458x430dd67co330ba5f5bd550f9c@mail.gmail.com \
    --to=srabbelier@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=mlm@aya.yale.edu \
    --cc=spearce@spearce.org \
    --cc=vcs-fast-import-devs@lists.launchpad.net \
    /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).