Re: "git fast-import" crashes parsing output from "fossil export --git"
- From
- Rowan Thorpe <rowan@rowanthorpe.com>
- Date
- Jan 29, 2018, 20:15 UTC
- Message-ID
- <CACgDUr6_LCMJaMcBBTfqTEH6nJfLKXRqu-HKMDanhqdLfHzbPA@mail.gmail.com>
- In-Reply-To
- <20180129171127.17097-1-szeder.dev@gmail.com>
On 29 January 2018 at 19:11, SZEDER Gábor <szeder.dev@gmail.com> wrote:
Show 21 quoted lines
> > ..[snip]..
> > Just commit some weird filenames, even one with a newline in it, to
> > test the code.
> > from :26779
> > M 100644 :427 :abc
> > M 100644 :10049 abc
> > def.txt
>
> A path like this must be quoted. Quoting from 'git fast-import'
> manpage:
>
> A <path> string must use UNIX-style directory separators (forward
> slash /), may contain any byte other than LF, and must not start
> with double quote (").
>
> A path can use C-style string quoting; this is accepted in all
> cases and mandatory if the filename starts with double quote or
> contains LF. In C-style quoting, the complete name should be
> surrounded with double quotes, and any LF, backslash, or double
> quote characters must be escaped by preceding them with a backslash
> (e.g., "path/with\n, \\ and \" in it").Ah, thanks. I had skimmed that manpage quickly but obviously too quickly and somehow missed that paragraph. I will post the bug-report at Fossil, where it belongs. Sorry for the noise.