From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Alexander Gavrilov <angavrilov@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH] Support copy and rename detection in fast-export.
Date: Mon, 21 Jul 2008 12:17:47 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807211207470.3305@eeepc-johanness> (raw)
In-Reply-To: <200807211216.01694.angavrilov@gmail.com>
Hi,
On Mon, 21 Jul 2008, Alexander Gavrilov wrote:
> Although it does not matter for Git itself, tools that
> export to systems that explicitly track copies and
> renames can benefit from such information.
>
> This patch makes fast-export output correct action
> logs when -M or -C are enabled.
I like it.
> I'm thinking about Git->SVN conversion, like
> http://repo.or.cz/w/git2svn.git
>
> The trouble with this patch is that old versions of fast-export
> accept -M and -C, but produce garbage if they are specified.
> So the only way for the users to ensure that it is supported is
> to check the git version (or directly test it).
Unfortunately, this is so.
> As a somewhat related question, in which order does fast-export
> output the commits, beside topological? In particular, does it order
> commits on parrallel branches (i.e. not topologically dependent) by
> date?
AFAIR it obeys topological order first, and then date order, by default.
This can be changed by --topo-order.
But before you go and try to support more options with fast-export: Some
options do not make sense, such as --reverse, "a...b", --skip, etc.
I do not even think we need to bother about die()ing with such options:
the user should know what she is doing with fast-export.
Ciao,
Dscho
next prev parent reply other threads:[~2008-07-21 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 8:16 [RFC PATCH] Support copy and rename detection in fast-export Alexander Gavrilov
2008-07-21 10:17 ` Johannes Schindelin [this message]
2008-07-26 18:49 ` [PATCH v2] " Alexander Gavrilov
2008-07-26 20:21 ` Shawn O. Pearce
2008-07-26 20:52 ` Alexander Gavrilov
2008-07-29 16:11 ` Junio C Hamano
2008-07-29 16:45 ` Shawn O. Pearce
2008-07-30 9:10 ` Alexander Gavrilov
2008-07-30 18:35 ` 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.0807211207470.3305@eeepc-johanness \
--to=johannes.schindelin@gmx.de \
--cc=angavrilov@gmail.com \
--cc=git@vger.kernel.org \
/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