Paul Mackerras wrote:
Something like that, I think, but to be sure I'd like to see the
actual author and committer lines that are causing the problem. Could
you send me the output of "git cat-file commit" on one of the
problematic commits?
I've created a small script that creates a minimal repo that shows
the problem...
ciao,
Torsten.
#!/bin/bash
#
# Script to generate git commit messages that
# contain windows style user names. This kind of
# names are generated when using git-svn with a
# svn-repo that uses NTLM authentification.
#
EXT="@23e39a30-19ad-a625-8bac-5c9ab2323746"
do_commit () {
F=test.txt
echo "test$1" > "$F"
git add "$F"
M="<$2$EXT>"
GIT_AUTHOR_NAME="$2" \
GIT_AUTHOR_EMAIL="$M" \
GIT_COMMITTER_NAME="$2" \
GIT_COMMITTER_EMAIL="$M" \
git commit -m "commit $1"
}
DIR=`mktemp -d /tmp/gitk-test.XXXXXXXXXX` || exit 1
trap "rm -rf \"$DIR\"" EXIT
cd $DIR || exit 2
git init
do_commit 1 "paul"
do_commit 2 "WIN\paul"
do_commit 3 "WIN\test"
do_commit 4 "WIN\nobody"
do_commit 5 "WIN\paul"
do_commit 6 "paul"
gitk
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
