git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lisandro Damián Nicanor Pérez Meyer" <perezmeyer@gmail.com>
To: git@vger.kernel.org
Subject: [wishlist] support git flow-like view
Date: Tue, 20 Nov 2012 20:42:52 -0300	[thread overview]
Message-ID: <201211202043.00293.perezmeyer@gmail.com> (raw)

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

Hi! I am not suscribed to the list, so please CC-me.

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...)

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.

Kinds regards, Lisandro.

[0] <http://nvie.com/posts/a-successful-git-branching-model/>


-- 
Esperando confirmación de ingredientes necesarios
que serán expuestos a la radiación...
  Manera geek de expresar que se espera la compra
  de carne para un típico asado argentino.
  Silvio Rikemberg.

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-20 23:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 23:42 Lisandro Damián Nicanor Pérez Meyer [this message]
2012-11-20 23:56 ` [wishlist] support git flow-like view 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)
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=201211202043.00293.perezmeyer@gmail.com \
    --to=perezmeyer@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 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).