From: Junio C Hamano <gitster@pobox.com>
To: Fabian Emmes <fabian.emmes@rwth-aachen.de>
Cc: git@vger.kernel.org, Lars Noschinski <lars@public.noschinski.de>,
Frank Lichtenheld <frank@lichtenheld.de>,
Martin Langhoff <martin@catalyst.net.nz>
Subject: Re: [PATCH] cvsserver: change generation of CVS author names
Date: Sat, 03 Jan 2009 14:14:51 -0800 [thread overview]
Message-ID: <7vwsdc3ulg.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1230910814-32307-2-git-send-email-fabian.emmes@rwth-aachen.de> (Fabian Emmes's message of "Fri, 02 Jan 2009 16:40:14 +0100")
Fabian Emmes <fabian.emmes@rwth-aachen.de> writes:
> CVS username is generated from local part email address.
> We take the whole local part but restrict the character set to the
> Portable Filename Character Set, which is used for Unix login names
> according to Single Unix Specification v3.
>
> Signed-off-by: Fabian Emmes <fabian.emmes@rwth-aachen.de>
> Signed-off-by: Lars Noschinski <lars@public.noschinski.de>
Stating "we should have done this from day one" is one thing (even though
"because some standard says so" is not particularly a good justification
without "and matches the way people use CVS in the real world in practice"
appended to it).
"We should suddenly change the behaviour" is quite a different thing and
it depends on what follows that sentence if the change is justifiable. We
do not want to hear "...; screw the existing repositories if they have
nonconforming names.". It is Ok if it is "...; existing repositories will
be affected, but the damage is limited to very minor set of operations,
namely X, Y and Z".
In other words, is there any backward compatibility issue when a
repository that has served existing CVS users and checkouts with older
version switches to the patched one? If there is one, is that grave
enough that we should care?
> git-cvsserver.perl | 12 +++++++++---
> 1 files changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/git-cvsserver.perl b/git-cvsserver.perl
> index cbcaeb4..fef7faf 100755
> --- a/git-cvsserver.perl
> +++ b/git-cvsserver.perl
> @@ -2533,12 +2533,18 @@ sub open_blob_or_die
> return $fh;
> }
>
> -# Generate a CVS author name from Git author information, by taking
> -# the first eight characters of the user part of the email address.
> +# Generate a CVS author name from Git author information, by taking the local
> +# part of the email address and replacing characters not in the Portable
> +# Filename Character Set (see IEEE Std 1003.1-2001, 3.276) by underscores. CVS
> +# Login names are Unix login names, which should be restricted to this
> +# character set.
> sub cvs_author
> {
> my $author_line = shift;
> - (my $author) = $author_line =~ /<([^>@]{1,8})/;
> + (my $author) = $author_line =~ /<([^@>]*)/;
> +
> + $author =~ s/[^-a-zA-Z0-9_.]/_/g;
> + $author =~ s/^-/_/;
>
> $author;
> }
next prev parent reply other threads:[~2009-01-03 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 15:40 [PATCH] cvsserver: add option to configure commit message Fabian Emmes
2009-01-02 15:40 ` [PATCH] cvsserver: change generation of CVS author names Fabian Emmes
2009-01-03 22:14 ` Junio C Hamano [this message]
2009-01-04 11:13 ` Lars Noschinski
2009-01-06 8:18 ` Junio C Hamano
2009-01-04 10:01 ` [PATCH] cvsserver: add option to configure commit message Junio C Hamano
2009-01-04 11:23 ` Lars Noschinski
2009-01-04 19:20 ` Junio C Hamano
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=7vwsdc3ulg.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=fabian.emmes@rwth-aachen.de \
--cc=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=lars@public.noschinski.de \
--cc=martin@catalyst.net.nz \
/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).