git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: martin f krafft <madduck@madduck.net>
To: git discussion list <git@vger.kernel.org>
Subject: Re: [PATCH] translate bad characters in refnames during git-svn fetch
Date: Mon, 16 Jul 2007 19:47:31 +0200	[thread overview]
Message-ID: <20070716174731.GA4792@lapse.madduck.net> (raw)
In-Reply-To: <20070716111509.GC18293@efreet.light.src> <20070716033050.GA29521@muzzle>

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

also sprach Eric Wong <normalperson@yhbt.net> [2007.07.16.0530 +0200]:
> The major issue with this is that it doesn't handle odd cases
> where a refname is sanitized into something (say "1234~2"
> sanitizes to "1234=2"), and then another branch is created named
> "1234=2".

Well, we can't please everyone, can we? :)

I like Jan's proposal about using the % escape, even though it
doesn't make pretty branch names.

On the other hand, we could make the translation regexps
configurable...

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
spamtraps: madduck.bogus@madduck.net
 
"if they can get you asking the wrong questions,
 they don't have to worry about answers."
                                                     -- thomas pynchon

[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-16 17:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-15 13:05 [PATCH] translate bad characters in refnames during git-svn fetch martin f krafft
2007-07-16  3:30 ` Eric Wong
2007-07-16 11:15   ` Jan Hudec
2007-07-16 17:47     ` martin f krafft [this message]
2007-07-17 12:28       ` Eric Wong
2007-07-17 13:17         ` martin f krafft
2007-07-26 10:59           ` Robert Ewald
2007-07-26 12:35             ` Martin F Krafft
2007-07-28  7:23         ` Mike Hommey
2007-07-28  7:33           ` David Kastrup

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=20070716174731.GA4792@lapse.madduck.net \
    --to=madduck@madduck.net \
    --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).