From: Chris Lamb <lamby@debian.org>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-rebase--interactive: Handle commit messages that end in backslash
Date: Thu, 13 May 2010 13:58:07 +0100 [thread overview]
Message-ID: <20100513135807.548594f9@bobcat.office> (raw)
In-Reply-To: <20100513133955.05493175@bobcat.office>
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
Chris Lamb wrote:
> This patch fixes three issues with handling commits that end in a
> backslash character ("\"), two of which had potential for silent data
> "loss".
Disregard the patch; it has some funky side-effect which breaks ONTO
parsing and I don't know why.
(The problem still exists though.)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` lamby@debian.org
`-
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-13 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 12:39 [PATCH] git-rebase--interactive: Handle commit messages that end in backslash Chris Lamb
2010-05-13 12:58 ` Chris Lamb [this message]
2010-05-13 14:33 ` Jeff King
2010-05-14 10:15 ` Thomas Rast
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=20100513135807.548594f9@bobcat.office \
--to=lamby@debian.org \
--cc=git@vger.kernel.org \
/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).