From: "Holger Hellmuth (IKS)" <hellmuth@ira.uka.de>
To: "Lisandro Damián Nicanor Pérez Meyer" <perezmeyer@gmail.com>
Cc: Andrew Ardill <andrew.ardill@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [wishlist] support git flow-like view
Date: Wed, 21 Nov 2012 15:52:05 +0100 [thread overview]
Message-ID: <50ACEA95.9020909@ira.uka.de> (raw)
In-Reply-To: <201211202113.44459.perezmeyer@gmail.com>
Am 21.11.2012 01:13, schrieb Lisandro Damián Nicanor Pérez Meyer:
> Well, two ideas come to my mind:
>
> - detect when using git flow (.git/config contains [gitflow "some_branch"]
> entries).
Shouldn't it be part of the gitflow package then?
> - Show "swim-lane"-like graphs, including branches that may not be present,
> but where there (release branches often are created and merged back, for
> example)
As a general feature there could be a config option gitk reads with an
ordered list of branch names (with wildcards). Those branches would
always be printed in gitk as the leftmost branches (i.e. have their own
lane on the left side). All other branches would be shown normally.
This would give you part of what you want, a special lane at least for
master and develop and for branches you can group under wildcard branch
names (for example if you prefix all release branches with "rel-").
And it would give others the ability to make special branches in gitk
more visible.
(Yes I know, I'm talking again of stuff I won't have time or ability to
implement ;-). Sigh)
next prev parent reply other threads:[~2012-11-21 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 23:42 [wishlist] support git flow-like view Lisandro Damián Nicanor Pérez Meyer
2012-11-20 23:56 ` Andrew Ardill
2012-11-21 0:13 ` Lisandro Damián Nicanor Pérez Meyer
2012-11-21 1:54 ` Andrew Ardill
2012-11-21 7:01 ` Johannes Sixt
2012-11-21 14:52 ` Holger Hellmuth (IKS) [this message]
2012-11-21 16:43 ` Lisandro Damián Nicanor Pérez Meyer
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=50ACEA95.9020909@ira.uka.de \
--to=hellmuth@ira.uka.de \
--cc=andrew.ardill@gmail.com \
--cc=git@vger.kernel.org \
--cc=perezmeyer@gmail.com \
/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).