From: Heiko Voigt <hvoigt@hvoigt.net>
To: git@vger.kernel.org
Cc: spearce@spearce.org
Subject: [RFC PATCH 0/8] Extend git gui for better "centralized" workflow integration
Date: Mon, 21 Sep 2009 15:06:47 +0200 [thread overview]
Message-ID: <cover.1253481338.git.hvoigt@hvoigt.net> (raw)
This series is adding some more support for a centralized workflow with
code review based on feature branches. Most of it is plugging existing
functionality together so the most typical steps can be done at once.
In our team at $dayjob we use a workflow were each developer creates
feature branches and once he is satified with his change he sends out a
review request to another developer (the reviewer) which is most
familiar with the code parts involved in the change. If the reviewer
likes the change he merges it into the upstream branch (master). He then
publishes the new master and deletes the feature branch. Thats a quick
description of the workflow I am trying to add more support for with
this series.
There are still some TODO markers in there and if someone can help me
with those I would be very glad. This is the first time I am doing some
more extensive programming in tcl/tk and git gui so I hope you do not
tear everything apart ;)
The last patch is not really about the same topic but since it currently
relies on the changes of this series I included it nevertheless.
cheers Heiko
Heiko Voigt (8):
git gui: add a "compose review email" checkbox to push dialog
git gui: teach delete dialog to open with a default remote
git gui: add checkbox to launch remote branch delete after push
git gui: teach fetch operation to close dialog on successful
completion
git gui: do fetch from a default remote on startup
git gui: add "review topic" menuitem which supports feature branch
workflow
Add documentation for git gui variables for email and delete after
push
git gui: make gc hint and fetch on startup sequential
Documentation/config.txt | 30 ++++++++++
git-gui/git-gui.sh | 29 ++++++++-
git-gui/lib/console.tcl | 6 ++
git-gui/lib/merge.tcl | 83 ++++++++++++++++++++++++--
git-gui/lib/option.tcl | 5 ++
git-gui/lib/remote_branch_delete.tcl | 6 +-
git-gui/lib/transport.tcl | 107 ++++++++++++++++++++++++++++++++-
7 files changed, 250 insertions(+), 16 deletions(-)
next reply other threads:[~2009-09-21 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 13:06 Heiko Voigt [this message]
2009-09-21 13:06 ` [RFC PATCH 1/8] git gui: add a "compose review email" checkbox to push dialog Heiko Voigt
2009-09-21 13:06 ` [RFC PATCH 2/8] git gui: teach delete dialog to open with a default remote Heiko Voigt
2009-09-21 13:06 ` [RFC PATCH 3/8] git gui: add checkbox to launch remote branch delete after push Heiko Voigt
2009-09-21 13:06 ` [RFC PATCH 4/8] git gui: teach fetch operation to close dialog on successful completion Heiko Voigt
2009-09-21 13:06 ` [RFC PATCH 5/8] git gui: do fetch from a default remote on startup Heiko Voigt
2009-09-21 13:06 ` [RFC PATCH 6/8] git gui: add "review topic" menuitem which supports feature branch workflow Heiko Voigt
2009-09-21 13:06 ` [RFC PATCH 7/8] Add documentation for git gui variables for email and delete after push Heiko Voigt
2009-09-21 13:06 ` [RFC PATCH 8/8] git gui: make gc hint and fetch on startup sequential Heiko Voigt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1253481338.git.hvoigt@hvoigt.net \
--to=hvoigt@hvoigt.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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.
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 NNTP newsgroup(s).