Pushing also makes the trac server read the changes from the git repo, which is kind of slow. But it doesn't have any excuse to be that slow. My record was about an hour, so far. But I haven't had time to debug this further, though. You can interrupt git when it is apparently hanging, though. The commit has already been recorded at that point.
We should probably have a look at alternatives for displaying git diffs, and possibly disable the git trac plugin. On Wednesday, December 18, 2013 10:41:26 PM UTC, Peter Bruin wrote: > > John Cremona wrote: > > git push --set-upstream trac intpoints:u/cremona/trac10973intpts >> >> The last operation took quite a while (10 minutes?) >> > > I noticed this too; what is causing this? Pushing one very small commit > (669 bytes according to git push -v) took a comparable time for me. > > Peter > > -- You received this message because you are subscribed to the Google Groups "sage-git" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
