From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 01 Sep 2011 16:00:05 GMT
Subject: Re: git-svn and mergeinfo
Message-ID: <7vfwkgxnga.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20110901104327.14d4dba6@robyn.woti.com>

Bryan Jacobs <bjacobs@woti.com> writes:

>> Naive question: why can't you pass a newline (properly quoted, of
>> course) directly within the string argument to the --mergeinfo option?
>
> The only way I know of to do that in bash is to assign the
> newline-bearing string to a variable, and then use the variable in a
> command line option. Extremely awkward.

Hmm, I think Michael meant by "properly quoted" something like this:

    $ git commit -s -m 'Fix blorb
    > 
    > As it stands, blorb feature is totally broken for such and
    > such reasons. Fix it by restructuring frotz and nitfol to
    > use the same xyzzy helper function.'

which is not all that awkward, even for a free-form text argument like
commit log. In this case, you are talking about svn merge-info that is a
lot more structured (it is much less likely to see a single-quote in there
than my commit log message example above, for example) so...