From: Mark Nauwelaerts <mark.nauwelaerts@gmail.com>
To: Hareesh Rajan <hareesh.rajan@gmail.com>, git@vger.kernel.org
Subject: Re: Git remote helper's fast export options
Date: Fri, 02 Feb 2018 10:49:28 +0100 [thread overview]
Message-ID: <5A743428.6040804@gmail.com> (raw)
In-Reply-To: <CAPm4vt=oAa848JqVHeOK28+qf6KoM56_JEWzZjou7X_-fFsk3w@mail.gmail.com>
On 01/02/18 00:14, Hareesh Rajan wrote:
> Hi,
>
> I use git remote helper to export/import repository content. Git
> internally uses fast-export command and it seems like the options to
> detect move and copy (-M/-C) are not being used.
> Logging this issue requesting a fix to the remote helper to generate
> rename and copy commands in the output dump.
>
> Git version: 2.14.1
>
> Thanks,
> Hareesh
This may have to do with a few changes that happened there recently; see
https://public-inbox.org/git/1514112729-31647-1-git-send-email-mark.nauwelaerts@gmail.com/
for a few patches addressing that.
Mark.
prev parent reply other threads:[~2018-02-02 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPm4vtnDdF31wx2VrarGk_uX9zQOubiD+LA7gsP_9qKFpqt28g@mail.gmail.com>
2018-01-31 23:14 ` Git remote helper's fast export options Hareesh Rajan
2018-02-02 9:49 ` Mark Nauwelaerts [this message]
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=5A743428.6040804@gmail.com \
--to=mark.nauwelaerts@gmail.com \
--cc=git@vger.kernel.org \
--cc=hareesh.rajan@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).