From: john at keeping.me.uk (John Keeping)
Subject: [PULL] Fix escaping in atom output
Date: Sat, 18 Feb 2017 17:41:01 +0000 [thread overview]
Message-ID: <20170218174101.GG1577@john.keeping.me.uk> (raw)
Hi Jason,
[Apologies for sending this twice, I forgot to add the list on the first
attempt.]
The following changes since commit be39d22328f841536b8e44e8aaeed80a74ebb353:
ui-patch: fix crash when using path limit (2017-01-23 18:36:04 +0100)
are available in the git repository at:
git://git.zx2c4.com/cgit jk/for-jason
for you to fetch changes up to 8d03b82036d45cd6e378b3696c22d8e356f8bb88:
ui-atom: properly escape delimiter in page link (2017-02-18 16:34:52 +0000)
This patch was originally posted at [0] and hasn't had any comment for
over a month, but our output is clearly wrong here.
[0] https://lists.zx2c4.com/pipermail/cgit/2017-January/003454.html
----------------------------------------------------------------
John Keeping (1):
ui-atom: properly escape delimiter in page link
ui-atom.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2017-02-18 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 17:41 john [this message]
2017-02-18 21:48 ` Jason
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=20170218174101.GG1577@john.keeping.me.uk \
--to=cgit@lists.zx2c4.com \
/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).