From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org, vcs-fast-import-devs@lists.launchpad.net
Subject: Re: What's cooking in git.git (Oct 2009, #01; Wed, 07)
Date: Thu, 29 Oct 2009 11:54:35 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.1.00.0910291151330.3687@felix-maschine> (raw)
In-Reply-To: <fabb9a1e0910281508m3e9bb8a6g7b39abc29fceae78@mail.gmail.com>
Hi,
On Wed, 28 Oct 2009, Sverre Rabbelier wrote:
> On Thu, Oct 8, 2009 at 10:58, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> > I think it makes to ignore options that are not for our vcs, as long
> > as options that change import behavior (such as marks, date-format)
> > are combined with, say, 'feature tool=git'. This way we can be sure
> > that when outputting out a vcs specific stream, it is only parsed by
> > that vcs.
> >
> > Note: yes, I know that marks and date-format are features now, but
> > there's really no other suitable example that I could think of).
> >
> > vcs fast import devs please ack this idea (and perhaps suggest
> > something other than "feature tool=git" if preferable) so that I can
> > reroll my gfi-options series :).
>
> Shawn, what do you want to do with this, it seems the vcs devs are not
> very interested in this feature, should I implement it as described
> above? That is:
> * If you use any option that is stream-changing you should include
> "feature tool=git" in your stream
> * import-marks and export-marks are made into features
> * "option vcs" is ignored if vcs is a different vcs
> * "option vcs" must be recognised if vcs is this vcs
It would be quite nice if this issue moved forward for a change.
As a consequence of it moving forward, I could nudge Sverre into
continuing with his git-remote-hg work that will allow me to work
transparently on a Mercurial repository using Git.
Transparent as in "no hassles".
It also will serve nicely as a perfect excuse to fix some design mistakes
in the foreign vcs stuff.
Ciao,
Dscho
next prev parent reply other threads:[~2009-10-29 10:54 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 [this message]
2009-10-30 3:50 ` 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=alpine.DEB.1.00.0910291151330.3687@felix-maschine \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=srabbelier@gmail.com \
--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).