From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: [PATCH] Avoid ambiguities when prettifying snapshot names
Date: Sat, 2 Jul 2016 22:04:02 +0200 [thread overview]
Message-ID: <CAHmME9p=ZUxLPVgE+9XkEedJ_8wBfsN2A=cM4Dm-uKtXdn16Kg@mail.gmail.com> (raw)
In-Reply-To: <20160524161518.9839-1-lfleischer@lfos.de>
Hey Lukas,
I'll probably merge this patch this week. It's a good basis for
another fix I'm working on with snapshot names for tags that include a
forward-slash ('/') character.
Jason
next prev parent reply other threads:[~2016-07-02 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 4:57 Snapshot URLs can conflict with two similar but unique tags wub
2016-05-23 5:11 ` wub
2016-05-24 16:15 ` [PATCH] Avoid ambiguities when prettifying snapshot names lfleischer
2016-07-02 13:30 ` lfleischer
2016-07-02 20:04 ` Jason [this message]
2016-07-05 14:13 ` 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='CAHmME9p=ZUxLPVgE+9XkEedJ_8wBfsN2A=cM4Dm-uKtXdn16Kg@mail.gmail.com' \
--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).