svn: E155007: '[...]\src' is not a working copy
yes windows -.-
here it takes at least 15min. The slowness seems to be in git svn info. I will look into it...
elif git log --max-count=1 >/dev/null 2>&1; then
echo "Using 'git log --graph' to get the revision"
REV=`git log --graph | grep 'git-svn-id' | head -n 1 | grep -o -e "@\([0-9]*\)" | tr -d '@ '`
LCD=`git log --date=iso --max-count=1 | grep -o -e "Date: \(.*\)" | cut -d ' ' -f 2- | sed 's/^ *//' | cut -f -2 -d ' '`
else
Hi.
i have found a possible speed up for this problem. If i use "git svn find-rev" instead of "git svn log" then i have a speed up of 6000% ;)
patch is attached
there is only a different date format if you use the git version, because i can't modify the git date output to look like the svn output...
greetings
ps. this is again a git patch...
pss. Am i really the only one with the speed problems of "git svn log" ? git version 1.8.4.msysgit.0 (it doesn't work from msys as from the cmd)
[edit] The patch had a view bugs...
does the patch work?The patch can not work, if the last commit is just a local one, because in this case the hash is not related to an svn revision.
Hi,
every time i build c::b from a git repo (https://github.com/obfuscated/codeblocks_sf/tree/no_ui_sdk) i getCodeand autorevision starts a huge tree of git/perl executables. I don't know what exactly they are doing but this operation is taking a huge amount of time, every time i build c::b (and this is are a lot of times lately)svn: E155007: '[...]\src' is not a working copy
I use git-svn (portablemsysgit+tortoisegit under Windows)for half a year, I don't have such issue. But obviously I don't put the bin folder of msysgit in PATH, so my build C::B always show a "0" in the revision dialog. :)
Basically, the msysgit command can only be used in a bash shell (in msys prompt), not the normal Windows command line.
As a quick fix I just removed the pre-build command from sdk build and provided custom autorevision.h with "const unsigned int svn_revision = 0;" etc. Can this cause any issues for Code::Blocks and it's plugins, or is the svn revision only used to display it/create changelog?No, but it should stay away from official svn trunk:)
[...]
I don't see how you could patch the tool in a meaningful way either because not only is a git commit .... what is it called, checksum (?) like 773dea65156909838fa6c22825cafe090ff8030 not valid, and unwieldy, and it also probably won't play well with the layout on the start page.