Hey, On Sun, Sep 6, 2009 at 3:15 PM, Johannes Gilger<[email protected]> wrote: > > Hi everyone, > > I've been busy over the weekend and the result of my work can be seen on > my various branches. Right now I've 4 branches on GitHub which imho > should all still go into 0.7. Im running the build from the combination > of these branches and haven't yet encountered a crash or a bug.
Thanks, I've been working on this a bit too. > My branches are: > jg/describe * I've applied this to my own branch, with a less intrusive patch to the .xib, so it's easily rebased et.c > doc * Looks sensible, I'll apply it when 0.7 is finished > dg/fsevents (contains bugfixes) I've worked with this a bit, but I don't think it's ready yet. For example, when rebasing, if the repository refreshes, you can get an error when both processes try to access the index, as one of them will already have the lock file. In that case the rebase fails midway, and there isn't a good way to resume it. That's not acceptable. The other thing is that the commit view refreshes too often. For example, when staging a file the whole commit view will refresh, which can take a long time on large repositories. I don't think this feature is ready yet. I'm not sure how to fix it, but we could do something by making sure the refresh doesn't use any index operations. I think at least we should disable the commit refresh part. Because of the intrusiveness of the autorefresh stuff, I think we should delay it for the next version. We can put it in master once 0.7 hits, and then see if we can fix it. If we aren't able to do that for the 0.8 timeframe, we can disable it again. > I've done extensive work on the doc-branch today, rewriting most of the > UserManual for GitX 0.7, including new screenshots and also updating the > homepage in a few spots. > The commit-messages speak for themselves, but since the diff for the > text is pretty useless I put up a version at > http://avalon.hoffentlich.net/~heipei/tmp/gitx/site/ As a nice > side-effect I also made almost the whole site W3C-valid ;) > Pieter: I'm sorry but in order to update the manual I made a few > assumptions about patches that still have to find their way into master > (like the SHA-column thing and the FSevents/preferences stuff). Thanks for working on this! Perhaps you can remove the autorefresh stuff for now? Then perhaps we can release 0.7 today.
