Bryan Jacobs <bjacobs@xxxxxxxx> 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...
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html