git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sverre Rabbelier <srabbelier@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>,
	Ian Clatworthy <ian.clatworthy@canonical.com>
Cc: 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: Fri, 30 Oct 2009 05:41:36 -0700	[thread overview]
Message-ID: <fabb9a1e0910300541w40d17242rbf0683654d97457f@mail.gmail.com> (raw)
In-Reply-To: <4AEA626D.8060804@canonical.com>

Heya,

On Thu, Oct 29, 2009 at 20:50, Ian Clatworthy
<ian.clatworthy@canonical.com> wrote:
>> On Thu, Oct 8, 2009 at 19:39, Shawn O. Pearce <spearce@spearce.org> wrote:
> Sverre Rabbelier wrote:
>> [edited Shawn's message somewhat to be more relevant to vcs-fast-import-dev]
>
> Thanks Sverre. Before I start, sorry for taking so long to reply to this.

Thanks for the review :).

> My strong preference is for:
>
> * feature = anything impacting semantics
> * option = tool-specific with no impact on semantics permitted.
>
> Both features and options ought to OS independent (where possible).

Even better, Shawn, if this LGTY I will reroll the series implementing this.

>>> I think we want to declare features for import-marks and export-marks
>>> and define these as paths to local files which store a VCS specific
>>> formatted mapping of fast-import mark numbers to VCS labels.
>
> Explicitly specifying the local path names worries me though. Consider someone
> using fastimport tools to maintain multiple mirrors in different tools.
> What should the stream look like then? Does it need to change if we want
> an additional mirror.

I think the stream should not have to change, which works if you
define the files to be local to the repo being exported to.  That is,
in git the line "feature export-marks=out.marks" would result in a
marks file located in "/path/to/repo/.git/fast-import/out.marks". Or
is that not what you mean?

> +1. By forcing tools to know about options specific to them, we avoid a
> range of bugs processing newer streams with older tools.

It is not possible to change the semantics using options though, what
kind of bugs could arise this way?

> I don't think options should be permitted to change import behavior. In
> other words, we should actively discourage vcs-specific streams

Sounds fair, I reckon that a wiki in addition to the
vcs-fast-import-devs list would not hurt :).

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2009-10-30 12:42 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
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 [this message]
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=fabb9a1e0910300541w40d17242rbf0683654d97457f@mail.gmail.com \
    --to=srabbelier@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=ian.clatworthy@canonical.com \
    --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).