{"thread":{"id":"9303","subject":"[ANNOUNCE] git-gui 0.8.0 now available","startedAt":"2007-07-30T05:38:00Z","lastAt":"2007-07-30T05:38:00Z","messageCount":1,"participants":["Shawn O. Pearce"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"49060","messageId":"20070730053800.GR20052@spearce.org","threadId":"9303","inReplyTo":null,"subject":"[ANNOUNCE] git-gui 0.8.0 now available","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-07-30T05:38:00Z","receivedAt":"2007-07-30T05:38:00Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"I've finally released git-gui 0.8.0.  Junio has already promised\nto include this version in git 1.5.3 when it gets released, but\nyou can also acquire it directly from my repo.or.cz repository:\n\n  gitweb:  http://repo.or.cz/w/git-gui.git/\n  fetch:   git://repo.or.cz/git-gui.git\n           http://repo.or.cz/r/git-gui.git\n\n\nChanges between 0.7.0 and 0.7.5:\n\n  Most of these changes have already been seen by a lot of users,\n  as they have been shipping with the maint releases of git 1.5.2\n  and the release candidates of 1.5.3.\n\n  * Completely rewritten blame viewer\n\n    The blame viewer was completely overhauled, with almost none of\n    the code from pre-0.7.0 surviving the rewrite.  The end result\n    is a viewer that actually offers a fast overview of how code\n    has moved around, and makes use of tooltips to display detailed\n    information quickly.\n\n  * new: Keybinding of Cmd-P/Ctrl-P for push action\n  * new: Push action button on left side toolbar\n\n  * bugfix: Prefer HEAD's message over MERGE_MSG when amending\n  * bugfix: Ensure Windows git-gui \"icons\" always end in .bat\n  * bugfix: ls-tree buffering error in tree browser\n  * bugfix: Work around ^{tree} shell error on MSYS\n  * bugfix: Avoid 'nice.exe' on MSYS\n\n\nChanges between 0.7.5 and 0.8.0:\n\n  Most of these new features haven't been merged into git.git yet,\n  but will be before 1.5.3 is released.\n\n  * Overhauled 'Starting Revision' UI for branch creation\n\n    The 'Starting Revision' part of the branch create dialog has\n    been rebuilt to better handle a large number of local and remote\n    tracking branches.  A glob-style filter can be applied to narrow\n    the list of choices.  Tooltips show the tip revision of each\n    branch, and also the last time the branch was last updated.\n\n    The new UI is much better suited to dealing with 200+ branches.\n\n  * Overhauled revision selection UI for checkout\n\n    The improved UI used for branch creation is also now used for\n    checkout, including local branches, remote tracking branches,\n    tags and arbitrary SHA-1 revision expressions.\n\n  * Overhauled revision selection UI for merge\n\n    Like checkout, merge uses the improved revision selection UI.\n    This allows users to merge arbitrary commits and not just\n    branches or tags.  It also avoids problems with long branch\n    names being clipped and not fully visible.\n\n  * Branch reset (aka git-branch -f) support\n\n    Local branches can be reset through Branch->Create.  This avoids\n    needing to delete the branch first, thereby saving the associated\n    reflog history.\n\n  * Automatically refetch tracking branches when needed\n\n    Before creating a new local branch or checking out a tracking\n    branch git-gui can first update the local tracking branch by\n    fetching it from the associated remote repository.\n\n    This feature helps users trying to work in a \"bound branch\"\n    workflow by making sure that they are always working with the\n    latest revision.\n\n  * Better detached HEAD support\n\n    git-gui now always works properly on detached HEAD and can switch\n    between local branches and detached HEAD.  The Branch->Checkout\n    menu option offers support for switching to a detached HEAD.\n\n    HEAD's reflog is now also updated similar to how core Git's\n    command line tools would update it.\n\n  * Browse any branch/revision and not just the current branch\n\n    The browser (and thus blame viewer) can now be opened for any\n    commit, not just the current branch.  The commit can be selected\n    using the improved revision selection UI already discussed above.\n\n  * Delete branches from remote repositories\n\n    If the remote repository is running git 1.5 or later you can\n    now delete remote branches through the Push->Delete menu.\n\n  * Prune local tracking branches via `git remote prune`\n\n    Pruning automatically deletes any tracking branches whose\n    corresponding remote branch has already been removed from the\n    remote repository.  A configuration option accessible in the\n    options dialog can enable this feature to run after each fetch.\n\n  * Blame/browser now works in bare repositories\n\n    The `git gui blame` and `git gui browser` command line\n    subcommands now work properly in a bare Git repository.\n    This makes it easier to use git-gui's blame viewer.\n\n  * More consistent blame/browser command line interface\n\n    Revision and path argument parsing for the blame and browser\n    subcommands is more consistent with each other and now behave\n    like the core git-blame argument parsing.\n\n  * Progress meter during checkout/reset operations\n\n    git-gui now scrapes the output of `git-read-tree -v` during a\n    branch checkout or reset and shows the progress meter in the\n    main window's status bar.  This lets users know how much work is\n    (roughly) remaining to complete the operation.\n\n  * Tracking branch merges are now formatted as pulls\n\n    When merging a tracking branch git-gui now generates the\n    commit message as though the branch was fetched+merged from the\n    remote using git-pull.  This makes for a cleaner merge commit\n    message, but does not incur the network IO that would normally\n    be associated with git-pull.\n\n  * Automatic commit message backup\n\n    The Edit->Undo action appears to cause Tk to crash on some\n    platforms.  To prevent users from losing the commit message\n    they were drafting git-gui now backs up the buffer to a file\n    every 2 seconds, if it has changed since the last backup.\n\n  * Removed 'octopus' merge support\n\n    It was decided recently on #git that octopus merge support is\n    not used often, and is probably not something users should be\n    commonly using.  It has been removed from git-gui entirely.\n\n  * Language change: \"to stage\" instead of \"to add\"\n\n    This improvement came from Christian Stimming as part of the\n    i18n work.  Although the command line uses git-add to stage\n    changes into the index we do tend to refer to this action as\n    \"staging\" and not \"adding\".  Christian's changes really clarify\n    the UI for English users and should help i18n translators to\n    find better translations in their target language.\n\n  * Misc. bug fixes and UI tweaks\n\n    A number of other bugs were fixed and some minor UI nits were\n    corrected.  For complete details please review the actual\n    commit history.\n\n\n0.8.0 testing history:\n\n  Just to give folks a little warm-n-fuzzy feeling about merging\n  so much new functionality into git 1.5.3 right before release,\n  I offer up this little tidbit:\n\n  I have a local git-gui user's group at my day-job made up of about\n  20 users, ranging in skill from \"novice computer user\" to \"expert\n  developer\".  They have been using version 0.8.0 on Cygwin for their\n  daily work for quite a while now and are reasonably happy with it.\n\n  Of course they also want even more features implemented.\n  Who doesn't.  ;-)\n\n-- \nShawn.\n"}]}