From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: What's new in git-gui.git
Date: Mon, 28 May 2007 18:49:49 -0400 [thread overview]
Message-ID: <20070528224949.GC7044@spearce.org> (raw)
I got around to working on git-gui this week. Yay me. Updates for
both the stable (0.7.x) series and the new development series
(0.8.x), and some roadmap items. See below...
--- Stable ---
The following changes since gitgui-0.7.1
Shawn O. Pearce (1):
git-gui: Gracefully handle bad TCL_PATH at compile time
are available in the git repository at:
repo.or.cz:/srv/git/git-gui.git maint
Shawn O. Pearce (3):
git-gui: Tighten internal pattern match for lib/ directory
Correct key bindings to Control-<foo>
git-gui: Guess our share/git-gui/lib path at runtime if possible
Makefile | 12 ++++++++++--
git-gui.sh | 17 +++++++++--------
2 files changed, 19 insertions(+), 10 deletions(-)
The final commit in this series has been tagged as gitgui-0.7.2
and should be packaged as part of the next maintenance release of
git 1.5.2. All are trivial fixes for minor issues raised since
0.7.1 was released.
--- Development ---
The following changes since gitgui-0.7.2
Shawn O. Pearce (1):
git-gui: Guess our share/git-gui/lib path at runtime if possible
are available in the git repository at:
repo.or.cz:/srv/git/git-gui.git master
Shawn O. Pearce (9):
git gui 0.8.0
git-gui: GUI support for running 'git remote prune <name>'
git-gui: Show the git-gui library path in 'About git-gui'
git-gui: Enable verbose Tcl loading earlier
git-gui: Provide fatal error if library is unavailable
git-gui: Disable tearoff menus on Windows, Mac OS X
git-gui: Allow users to rename branches through 'branch -m'
git-gui: Allow users to delete remote branches
git-gui: Expose the merge.diffstat configuration option
GIT-VERSION-GEN | 2 +-
git-gui.sh | 87 +++++++----
lib/branch_rename.tcl | 137 +++++++++++++++++
lib/option.tcl | 17 ++-
lib/remote.tcl | 11 ++
lib/remote_branch_delete.tcl | 348 ++++++++++++++++++++++++++++++++++++++++++
lib/transport.tcl | 16 ++-
7 files changed, 586 insertions(+), 32 deletions(-)
create mode 100644 lib/branch_rename.tcl
create mode 100644 lib/remote_branch_delete.tcl
This is actually the start of the 0.8.0 development cycle. It is
stable enough for git.git's master branch. I don't anticipate this
version of git-gui being packaged with any git earlier than 1.5.3.
Some major new features have been added:
- Rename an existing branch (git-brach -m).
- Delete an existing remote branch.
- Prune expired tracking branches.
- Automatically prune expired tracking branches during fetch.
I'm hoping to do a lot more before 0.8.0 goes final. Which is part
of the reason why I don't expect this to be packaged with anything
earlier than 1.5.3.
--- Roadmap ---
Looking ahead, I'd like to see some improvement in the following
areas. It would be nice if some Tcl/Tk-minded individuals were
willing to dive and help. ;-)
- Initial repository creation
- Initial repository cloning
- Select an existing repository from an OS native file dialog
These are mostly about better supporting the MinGW environment
(or a Cygwin environment) where some users are not used to
performing operations through a command line terminal window.
Sometimes being able to start an application through an icon
and have it prompt you for initial configuration is exactly what
the user wants.
At the same time we probably should support running against a
bare repository, at least for the cases of the "browser" and
"blame" subcommands.
- Blame viewer coloring should be less horrid
- Blame viewer should support digging into the prior version
- Jump to line in blame viewer (use vi's :nnn syntax?)
- Find substring in blame viewer (use vi's / syntax?)
These have been discussed before. The current blame viewer is
useful, but not fun to look at. It also doesn't let you dig
back into history further than the revision it was started on.
Now that the blame viewer is cleaned up and uses git-gui's
"class/field/method" system this is probably a lot easier to
get done (pre-0.7.0 that code was just a disaster).
- Fetch+merge from arbitrary URL and branch(es)
Aka "git pull", but in a GUI. Pulling from random URLs is not
uncommon in the Git user community and we should support it as
a first-class operation in git-gui.
The UI I just put in for deleting remote branches may offer a
good starting point for this, as it does an async ls-remote to
get the available branch heads.
- Preserve author during amend
- Set commit author line
These sort of go hand-in-hand. Currently there is no way to enter
an author; the authorship of a commit is always the current user.
But I know a few people using git-gui who really should be doing
`git commit --author=$someoneelse` every once in a while, as
they are committing files for $someoneelse.
I'm also getting bit by the amend bug myself when I apply
patches from other people and then go back and try to tweak
something minor.
--
Shawn.
next reply other threads:[~2007-05-28 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 22:49 Shawn O. Pearce [this message]
2007-05-29 4:11 ` What's new in git-gui.git Shawn O. Pearce
2007-05-29 8:12 ` Alex Riesen
2007-05-29 10:59 ` Johannes Schindelin
2007-05-30 2:39 ` Shawn O. Pearce
2007-05-29 11:18 ` Petr Baudis
2007-05-30 2:34 ` Shawn O. Pearce
2007-05-29 7:46 ` Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070528224949.GC7044@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).