[git-users] Re: Odd performance problem with git diff
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 --since two weeks ago --until yesterday The arguments accepted are pretty versatile. For details, see the Specifying Revisions section of git-rev-parsehttp://www.kernel.org/pub/software/scm/git/docs/v1.5.0.7/git-rev-parse.html . I don't have any more ideas on figuring out what the performance bottleneck could be though, sorry. Maybe someone on the main git listhttp://vger.kernel.org/vger-lists.html#gitcan help more? -- 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. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] Re: Odd performance problem with git diff
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. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] Re: Odd performance problem with git diff
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: 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. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] Re: Running a dcommit for all branches
On Mar 23, 2:03 am, Thomas Ferris Nicolaisen tfn...@gmail.com wrote: Almost, this is how: git clone bare-url gitdir cd gitdir git svn init svn-url This is 5. Set up an SVN remote in the developer's repo in this guide:http://blog.tfnico.com/2010/11/git-svn-mirror-for-multiple-branches.html git branch mybranch remotes/origin/mybranch git co mybranch I had created the co alias for checkout and the upci alias. I tried this and modified a file followed by git commit -a -m test file update git upci It gave me an error message unable to determine upstream SVN information from HEAD history. Was there a step that I missed? -- 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. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] Re: Running a dcommit for all branches
git branch mybranch remotes/origin/mybranch git co mybranch I had created the co alias for checkout and the upci alias. I tried this and modified a file followed by git commit -a -m test file update git upci It gave me an error message unable to determine upstream SVN information from HEAD history. Was there a step that I missed? One note: I usually use git co -t origin/mybranch, so it is created as a tracking branch. This error message is very typical. It means that git-svn doesn't recognize which commits come from SVN. Usually you get this if the reference in .git/refs/remotes/[branch] is missing or wrong. It can also occur in some other situations that I can't remember from the top of my head. So it's hard to say. I would first step away from the upci alias for a bit, and use the manual update-ref + dcommit commands again, just to be sure that there's not a bug in the alias. Do this: git update-ref refs/remotes/[branch] refs/remotes/origin/[branch] ... followed by git svn dcommit. If this still doesn't work, please post back here with the following info, so I can make a more educated guess on what's wrong: 1. The output from git config -l 2. Log of the last few (say, 5) commits in SVN branch 3. Log of the last few commits in the git repo 4. Output from git remote show origin -- 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. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
