Yay! These .svn folders are causing havoc to our workspace in general.
Amazing how much they slow it down. Another good reason to switch to git :)
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email to
In the course of messing around with this issue, I discovered
something interesting. There were a number of .svn (Subversion)
directories in my repository because the git repository was created
from directories checked out of subversion. Also, a number of
those .svn directories contained binary
Yes, git log http://www.kernel.org/pub/software/scm/git/docs/git-log.htmlcan
take two times as arguments.
git log --since two weeks ago --until yesterday
You might also want to consider git
whatchangedhttp://www.kernel.org/pub/software/scm/git/docs/git-whatchanged.html
:
git whatchanged
Actually this was a much better guide to the git date formats:
http://www.alexpeattie.com/blog/working-with-dates-in-git/
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
Thanks for your help on this. Maybe I'll look into using git log
instead of git diff. I've never seen git whatchanged before so I'll
check that out too.
On Mar 24, 1:33 am, Thomas Ferris Nicolaisen tfn...@gmail.com wrote:
Actually this was a much better guide to the git date formats:
Wow, thanks for your detailed response, Thomas. I'll try to answer
some of your questions:
Both repositories are on a remote mounted filesystem. Several people
have told me that defeats the purpose of using git, but I claim
innocence by virtue of inheriting the system as it is. :-) Also, I
And, just to clarify, the following text:
On Mar 17, 10:32 am, Dave R dran...@yahoo-inc.com wrote:
Here is the command that's slow on repository #1, and fast on
repository #2:
is wrong. The command is fast on repository #1 and slow on repository
#2.
--
You received this message because you
Hi Dave,
Just to clarify: The normal way to check for changes in a repository is
usually this:
cd /path/to/repository
git status
There are many factors that come into play with git performance, and
although it is inherently fast compared to a remote repository system like
Subversion, it
