-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I'm using git version 1.7.1, and found a tiny bug:
mikelifeguard@arbour:~/git/perlwikibot (master)$ git svn info
Use of uninitialized value $lc_rev in concatenation (.) or string at
/usr/lib/git-core/git-svn line 1141.
...normal `git svn info` output...
Cheers,
- -Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkvriOcACgkQst0AR/DaKHsqSwCgzgLfkFDO+5PLedIi8Ud1s9eH
I3YAn1vr0abiUaxCDX8NfL0KPWwTgnF2
=TOzT
-----END PGP SIGNATURE-----
On Thu, May 13, 2010 at 02:06:53AM -0300, Mike.lifeguard wrote:
I'm using git version 1.7.1, and found a tiny bug:
mikelifeguard@arbour:~/git/perlwikibot (master)$ git svn info
Use of uninitialized value $lc_rev in concatenation (.) or string at
/usr/lib/git-core/git-svn line 1141.
this shouldn't happen unless you are doing git svn info in a tree
that has no metadata (or lost it somehow).
does git log show any git-svn-id tags?
Carlo
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10-05-13 05:40 AM, Carlo Marcelo Arenas Belon wrote:
this shouldn't happen unless you are doing git svn info in a tree
that has no metadata (or lost it somehow).
Even if your tree has no SVN metadata, perl shouldn't be sending me
errors. Maybe you want to catch the error and git-svn can give me the error.
does git log show any git-svn-id tags?
Yes, it did... though I've since re-cloned the SVN repo since I needed
to include stuff I had skipped with --ignore-paths. The top commit was
made to something I had ignored in that way. I don't know if git would
have lc_rev data in that case.
- -Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkvsE3wACgkQst0AR/DaKHvEuwCgkUZ/DF5GAQzwM38ICrkLaDkY
qWMAn28fO1Jzu2LHVnG7mrKRIM8ZIb+h
=eG8N
-----END PGP SIGNATURE-----