[ANNOUNCE] git-gui 0.7.0-rc1

[ANNOUNCE] git-gui 0.7.0-rc1

[Shawn O. Pearce]

There have been a good deal of changes in git-gui recently.
Most significantly within the inner workings.  The code has been
refactored into multiple files and I'm starting to make use of the
auto_load feature of Tcl, as well as Tcl namespaces.  As you can
see by the diffstat below I moved over 4000 lines out of git-gui.sh
and into other files.  ;-)

There were some minor tweaks to the git-gui Makefile variable
handling so I have pre-merged git-gui.git's master into git.git
master, handling those tweaks as part of the merge.  After pulling
it in you may also want to fetch from git-gui.git to grab the
gitgui-0.7.0-rc1 tag.

I'm tagging this release as rc1 as I hope to get a few more
improvements in this week, before I call it 0.7.0 final.

---

The following changes since commit 3082acfa7c626a34aa419a163585051c2df2bf09:
  Alex Riesen (1):
        Use GIT_OBJECT_DIR for temporary files of pack-objects

are available in the git repository at:

  repo.or.cz:/srv/git/git/fastimport.git gitgui-master

Shawn O. Pearce (16):
      git-gui: Include the subject in the status bar after commit
      git-gui: Warn users before making an octopus merge
      git-gui: Correct line wrapping for too many branch message
      git-gui: Cleanup common font handling for font_ui
      git-gui: Use option database defaults to set the font
      git-gui: Refactor to use our git proc more often
      git-gui: Track our own embedded values and rebuild when they change
      git-gui: Refactor into multiple files to save my sanity
      git-gui: Move console procs into their own namespace
      git-gui: Allow vi keys to scroll the diff/blame regions
      git-gui: Move merge support into a namespace
      git-gui: Show all possible branches for merge
      git-gui: Include commit id/subject in merge choices
      git-gui: Use vi-like keys in merge dialog
      Merge branch 'master' of git://repo.or.cz/git-gui
      Remove duplicate exports from Makefile

 Makefile                  |   18 +-
 git-gui/.gitignore        |    2 +
 git-gui/Makefile          |   38 +-
 git-gui/git-gui.sh        | 4121 ++-------------------------------------------
 git-gui/lib/blame.tcl     |  407 +++++
 git-gui/lib/branch.tcl    |  572 +++++++
 git-gui/lib/browser.tcl   |  263 +++
 git-gui/lib/commit.tcl    |  410 +++++
 git-gui/lib/console.tcl   |  201 +++
 git-gui/lib/database.tcl  |   89 +
 git-gui/lib/diff.tcl      |  336 ++++
 git-gui/lib/error.tcl     |  101 ++
 git-gui/lib/index.tcl     |  409 +++++
 git-gui/lib/merge.tcl     |  309 ++++
 git-gui/lib/option.tcl    |  290 ++++
 git-gui/lib/remote.tcl    |  159 ++
 git-gui/lib/shortcut.tcl  |  141 ++
 git-gui/lib/transport.tcl |  164 ++
 18 files changed, 4009 insertions(+), 4021 deletions(-)
 create mode 100644 git-gui/lib/blame.tcl
 create mode 100644 git-gui/lib/branch.tcl
 create mode 100644 git-gui/lib/browser.tcl
 create mode 100644 git-gui/lib/commit.tcl
 create mode 100644 git-gui/lib/console.tcl
 create mode 100644 git-gui/lib/database.tcl
 create mode 100644 git-gui/lib/diff.tcl
 create mode 100644 git-gui/lib/error.tcl
 create mode 100644 git-gui/lib/index.tcl
 create mode 100644 git-gui/lib/merge.tcl
 create mode 100644 git-gui/lib/option.tcl
 create mode 100644 git-gui/lib/remote.tcl
 create mode 100644 git-gui/lib/shortcut.tcl
 create mode 100644 git-gui/lib/transport.tcl
-- 
Shawn.

Re: [ANNOUNCE] git-gui 0.7.0-rc1

[Junio C Hamano]

"Shawn O. Pearce" <spearce@spearce.org> writes:

> I'm tagging this release as rc1 as I hope to get a few more
> improvements in this week, before I call it 0.7.0 final.

So we will expect git 1.5.2 to ship with 0.7.0 perhaps mid to
late next week?

Re: [ANNOUNCE] git-gui 0.7.0-rc1

[Shawn O. Pearce]

Junio C Hamano <junkio@cox.net> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
> 
> > I'm tagging this release as rc1 as I hope to get a few more
> > improvements in this week, before I call it 0.7.0 final.
> 
> So we will expect git 1.5.2 to ship with 0.7.0 perhaps mid to
> late next week?

Yes, that would be the plan.

-- 
Shawn.