From: Martin Langhoff <martin.langhoff@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Yakup Akbay <yakbay@ubicom.com>, git@vger.kernel.org
Subject: Re: Compact view of history in gitk
Date: Tue, 29 Sep 2009 17:21:44 +0200 [thread overview]
Message-ID: <46a038f90909290821g4bb9cecewace8c8a516b74c78@mail.gmail.com> (raw)
In-Reply-To: <4AC1F88E.7080802@viscovery.net>
On Tue, Sep 29, 2009 at 2:07 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> I think, --simplify-by-decoration comes close, even though it may not be
> 100% what you describe.
That is awesome.
Awesomer would be teaching gitk to expand (un-simplify) parts of it.
Probably a pig of a project to do though :-/
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2009-09-29 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 11:49 Compact view of history in gitk Yakup Akbay
2009-09-29 12:07 ` Johannes Sixt
2009-09-29 12:44 ` Yakup Akbay
2009-09-29 15:21 ` Martin Langhoff [this message]
2009-09-30 18:41 ` Dirk Süsserott
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=46a038f90909290821g4bb9cecewace8c8a516b74c78@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=yakbay@ubicom.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).