git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "martin f. krafft" <madduck@madduck.net>
Cc: git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>
Subject: Re: [PATCH] Escape project names before creating pathinfo URLs
Date: Mon, 21 Apr 2008 23:31:13 -0700	[thread overview]
Message-ID: <7vfxte4czy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1208726618-27477-1-git-send-email-madduck@madduck.net> (martin f. krafft's message of "Sun, 20 Apr 2008 23:23:38 +0200")

Both patches make sense; will apply to 'maint'.

      reply	other threads:[~2008-04-22  6:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-20 14:46 gitweb fails with pathinfo and project with ++ in the name martin f krafft
2008-04-20 15:53 ` Bug#476076: " Frank Lichtenheld
2008-04-20 21:03   ` martin f krafft
2008-04-20 21:03     ` [PATCH] Escape project name in regexp martin f. krafft
2008-04-20 21:23       ` [PATCH] Escape project names before creating pathinfo URLs martin f. krafft
2008-04-22  6:31         ` Junio C Hamano [this message]

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=7vfxte4czy.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=madduck@madduck.net \
    /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).