All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lisandro Damián Nicanor Pérez Meyer" <perezmeyer@gmail.com>
To: Andrew Ardill <andrew.ardill@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [wishlist] support git flow-like view
Date: Tue, 20 Nov 2012 21:13:36 -0300	[thread overview]
Message-ID: <201211202113.44459.perezmeyer@gmail.com> (raw)
In-Reply-To: <CAH5451nrcEo3Uxm0x6b39Hq1k-J4=OZPi-Cao7osaiS-w_Z1+Q@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1974 bytes --]

On Tue 20 Nov 2012 20:56:26 Andrew Ardill escribió:
> On 21 November 2012 10:42, Lisandro Damián Nicanor Pérez Meyer
> 
> <perezmeyer@gmail.com> wrote:
> > Hi! I am not suscribed to the list, so please CC-me.
> 
> That is the default etiquette on this list :)

Great :-)
 
> > I think this may have been proposed before, but I could not find anything
> > in the web, so I better try myself :)
> > 
> > The idea would be to gitk to show a "git flow-like"[0] view when it
> > detects git flow (or the user ask for it or...)
> 
> What does it mean to 'show a "git flow-like" view'? Show multiple
> branches? Place commits on each branch in 'swim-lanes', rather than
> moving them around on the horizontal to fit the space available? Some
> more detail, or even a mock-up would help a lot here.

I think the best mock-up would be:

<http://nvie.com/img/2009/12/Screen-shot-2009-12-24-at-11.32.03.png>

Yes, I'm referring to "swim-lanes" like view. Which may be already there and 
I'm miserably failing to see :-/

> > Basiccaly, you can show the main two branches: master and develop. Of
> > course, having the possibility to show feature/release/hotfixes branches
> > would be ideal.
> 
> It is already possible to show multiple branches in gitk at the same
> time. You probably have some more specific needs beyond simply showing
> the different branches. Maybe you can be more specific?

Well, two ideas come to my mind:

- detect when using git flow (.git/config contains [gitflow "some_branch"] 
entries).
- 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)

Maybe some of this is already there and/or it's too much trouble to do so, in 
those cases, please accept my apologies :-)

Kinds regards, Lisandro.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-11-21  0:14 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 [this message]
2012-11-21  1:54     ` Andrew Ardill
2012-11-21  7:01     ` Johannes Sixt
2012-11-21 14:52     ` Holger Hellmuth (IKS)
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=201211202113.44459.perezmeyer@gmail.com \
    --to=perezmeyer@gmail.com \
    --cc=andrew.ardill@gmail.com \
    --cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.