From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Eric Wong" <normalperson@yhbt.net>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] git-svn: sanitize_remote_name should accept underscores.
Date: Wed, 25 Jun 2008 11:01:11 -0400 [thread overview]
Message-ID: <32541b130806250801p1508d15axc610f335b8d235ef@mail.gmail.com> (raw)
In-Reply-To: <20080625074548.GA8984@hand.yhbt.net>
On 6/25/08, Eric Wong <normalperson@yhbt.net> wrote:
> No, nothing to do with DNS hostnames in the remote names. I think I
> just looked at remotes2config.sh one day and used it as a reference :x
>
> It's late and I've had a rough few days, but shouldn't
> sanitize_remote_name() just escape . and "? Right now it's converting
> stuff to . which has me very confused...
I think there might be higher-level problems here: what is it
sanitizing anyway, and why? If it found my D2007_Win32 svn-remote
entry in the config (as it seems to have done when trying to locate
its parent branch during fetch), and *then* it sanitized it to
D2007.Win32, that doesn't even make any sense. Clearly something
straight from the config file doesn't need to be sanitized.
However, I don't understand the code well enough to be able to say a)
whether that's exactly what happened, or b) other places where
sanitize_remote_name() *is* important, or c) whether
sanitize_remote_name() is even correct.
Have fun,
Avery
next prev parent reply other threads:[~2008-06-25 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 15:54 [PATCH/RFC] git-svn: sanitize_remote_name should accept underscores Avery Pennarun
2008-06-25 6:44 ` Eric Wong
2008-06-25 6:55 ` Eric Wong
2008-06-25 7:11 ` Junio C Hamano
2008-06-25 7:45 ` Eric Wong
2008-06-25 15:01 ` Avery Pennarun [this message]
2008-06-29 3:40 ` [PATCH] git-svn: don't sanitize remote names in config Eric Wong
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=32541b130806250801p1508d15axc610f335b8d235ef@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=normalperson@yhbt.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).