From: Dennis Schridde <devurandom@gmx.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-svn: handle leading/trailing whitespace from svnsync revprops
Date: Sat, 12 Jan 2008 13:34:18 +0100 [thread overview]
Message-ID: <200801121334.18632.devurandom@gmx.net> (raw)
In-Reply-To: <20080112071355.GA17021@soma>
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
Am Samstag, 12. Januar 2008 08:13:55 schrieben Sie:
> Repositories generated by svnsync cannot be relied on to have
> properly set revprops without newlines in UUIDs and URLs. There
> may be broken versions of svnsync out there that append extra
> newlines to UUIDs, or the revprops could've been changed by
> repository administrators at any time, too.
>
> At least one repository we've come across has an embedded
> newline erroneously set in the svnsync-uuid prop. This is bad
> because the trailing newline is taken as another record by the
> Git.pm library, and the wantarray detection causes tmp_config()
> to return an array with an empty-but-existing second element.
>
> We will now strip leading and trailing whitespace both before
> setting and after reading the uuid and url for svnsync values.
> We will also force tmp_config to return a single scalar when
> reading existing values.
>
> SVN UUIDs should never have whitespace in them, and SVN
> repository URLs should be URI-escaped, so neither of those
> values we ever see in git-svn should actually have whitespace
> in them.
>
> Thanks to Dennis Schridde for the bug report and Junio for
> helping diagnose this.
Thanks! This patch seems to work, at least the "Odd number..." message is
gone. The segfault with a non-debug perl stays, though. But I guess that is a
different problem.
--Dennis
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-12 12:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 16:38 Odd number of elements in anonymous hash Dennis Schridde
2008-01-08 17:21 ` Junio C Hamano
2008-01-08 17:30 ` Dennis Schridde
2008-01-10 8:38 ` Eric Wong
2008-01-10 11:04 ` Dennis Schridde
2008-01-10 17:13 ` Dennis Schridde
2008-01-10 20:08 ` Junio C Hamano
2008-01-10 21:13 ` Dennis Schridde
2008-01-10 21:45 ` Junio C Hamano
2008-01-12 7:13 ` [PATCH] git-svn: handle leading/trailing whitespace from svnsync revprops Eric Wong
2008-01-12 7:57 ` Junio C Hamano
2008-01-12 9:12 ` Eric Wong
2008-01-12 9:55 ` Björn Steinbrink
2008-01-12 18:57 ` Junio C Hamano
2008-01-12 19:31 ` Junio C Hamano
2008-01-12 12:34 ` Dennis Schridde [this message]
2008-01-09 22:58 ` Odd number of elements in anonymous hash Eric Wong
[not found] ` <200801240037.33908.devurandom@gmx.net>
[not found] ` <4797E894.8060706@vilain.net>
[not found] ` <200801241513.45088.devurandom@gmx.net>
2008-01-24 23:10 ` Sam Vilain
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=200801121334.18632.devurandom@gmx.net \
--to=devurandom@gmx.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).