jargij / gource

Automatically exported from code.google.com/p/gource
0 stars 0 forks source link

mercurial-gource breaks up filenames with spaces #24

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. create a mercurial repository with filenames containing spaces
2. run mercurial-gource.py

What is the expected output? What do you see instead?

Expected an entry for each filename, got an entry for each space-separated
filename component.

What version of the product are you using? On what operating system?

mercurial-gource 1.0, on win32

Please provide any additional information below.

I rewrote/refactored the script using Mercurial styles, which are one step
up from templates, and can format files individually.  Actually, a style
file would be sufficient if not for a date format mismatch.

http://bitbucket.org/JustinLove/stylish-mercurial-gource/

Original issue reported on code.google.com by sepiaton...@gmail.com on 5 Dec 2009 at 3:20

GoogleCodeExporter commented 8 years ago
Cool.

Since from the look of it Mercurial has similar-or-better quality log support 
to Git,
I think I might add some proper integration for it.

Gource can work out it been given a Mercurial directory, and invoke hg log with 
your
gource.style and I'll make it accept timestamps with sub second precision.

Original comment by acaudw...@gmail.com on 6 Dec 2009 at 10:23

GoogleCodeExporter commented 8 years ago
Mercurial support is now built in. Cheers!

Original comment by acaudw...@gmail.com on 12 Dec 2009 at 2:34

GoogleCodeExporter commented 8 years ago
Awesome, thanks.

One small problem though: the default log command comes out in reverse order, 
and
then gource processes it in file order.  You should pass -r 0:tip to put it in
forward order.  Did I miss a way to pass arguments through to the log command?

Original comment by sepiaton...@gmail.com on 12 Dec 2009 at 2:59

GoogleCodeExporter commented 8 years ago
Doh! Thanks for picking up on this. I've merged your commit and I'll update the 
release.

Cheers

Original comment by acaudw...@gmail.com on 12 Dec 2009 at 7:27