From: Bryan Jacobs <bjacobs@woti.com>
To: "Carlos Martín Nieto" <cmn@elego.de>
Cc: Michael Haggerty <mhagger@alum.mit.edu>, git@vger.kernel.org
Subject: Re: git-svn and mergeinfo
Date: Tue, 6 Sep 2011 09:52:56 -0400 [thread overview]
Message-ID: <20110906095256.205dd5d0@robyn.woti.com> (raw)
In-Reply-To: <1315313800.9839.10.camel@bee.lab.cmartin.tk>
On Tue, 06 Sep 2011 14:56:38 +0200
Carlos Martín Nieto <cmn@elego.de> wrote:
> You can also save the mergeinfo to a file, add the line, and use
> --mergeinfo=$(cat /tmp/some-file) to set it. It is indeed awkward, but
> blindly replacing every space with a newline is not always the right
> option. If a merged directory contains a space, this change will break
> the mergeinfo, even if you're properly quoting your variable or using
> the $(cat /some/file) method.
>
> Cheers,
> cmn
Ah, a situation I neglected to consider! Perhaps we should revert this
patch, since I worked up the initiative to write an
auto-populating-mergeinfo patch for git-svn anyhow.
Bryan Jacobs
next prev parent reply other threads:[~2011-09-06 13:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 17:20 git-svn and mergeinfo Bryan Jacobs
2011-08-29 19:26 ` git bug reporting Jeff King
2011-08-29 19:34 ` Bryan Jacobs
2011-08-29 20:44 ` Junio C Hamano
2011-08-31 14:03 ` Sverre Rabbelier
2011-08-31 13:59 ` git-svn and mergeinfo Sverre Rabbelier
2011-08-31 16:55 ` Bryan Jacobs
2011-08-31 17:01 ` Sverre Rabbelier
2011-09-01 8:59 ` Michael Haggerty
2011-09-01 14:43 ` Bryan Jacobs
2011-09-01 16:00 ` Junio C Hamano
2011-09-06 12:56 ` Carlos Martín Nieto
2011-09-06 13:52 ` Bryan Jacobs [this message]
2011-09-06 14:28 ` Carlos Martín Nieto
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=20110906095256.205dd5d0@robyn.woti.com \
--to=bjacobs@woti.com \
--cc=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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).