From: "Dirk Süsserott" <poststelle@suesserott.de>
To: Dirk Suesserott <newsletter@dirk.my1.cc>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] gitk: Added option 'Simple history' to the options menu
Date: Fri, 15 May 2009 21:59:19 +0200 [thread overview]
Message-ID: <4A0DC997.9040604@suesserott.de> (raw)
In-Reply-To: <12417222593716-git-send-email-newsletter@dirk.my1.cc>
Hi Junio,
some days ago I supplied a patch that adds the
'--simplify-by-decoration' switch to gitk's options menu. This was
inspired by Jakub Narebski's answer to 'How to restrict gitk to show
only branch/merge commits?'.
Have you just missed it or didn't it qualify for inclusion? I didn't
know that option and found it really helpful to get an overview about
the history of my projects.
What do the others think?
Cheers,
Dirk
Am 07.05.2009 20:50 schrieb Dirk Suesserott:
> When clicked, the option --simplify-by-decoration is added to gitk/git log.
> This yields to a simplified history where only decorated commits are shown,
> i.e. those with a yellow tag or a green branch flag.
>
> Signed-off-by: Dirk Suesserott <newsletter@dirk.my1.cc>
> ---
> gitk-git/gitk | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/gitk-git/gitk b/gitk-git/gitk
> index 1a7887b..f65cf2c 100644
> --- a/gitk-git/gitk
> +++ b/gitk-git/gitk
> @@ -3676,6 +3676,7 @@ set known_view_options {
> {all b * "--all" {mc "Use all refs"}}
> {dorder b . {"--date-order" "-d"} {mc "Strictly sort by date"}}
> {lright b . "--left-right" {mc "Mark branch sides"}}
> + {smplhst b . "--simplify-by-decoration" {mc "Simple history"}}
> {since t15 + {"--since=*" "--after=*"} {mc "Since date:"}}
> {until t15 . {"--until=*" "--before=*"} {mc "Until date:"}}
> {limit t10 + "--max-count=*" {mc "Max count:"}}
prev parent reply other threads:[~2009-05-15 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 18:50 [PATCH] gitk: Added option 'Simple history' to the options menu Dirk Suesserott
2009-05-15 19:59 ` Dirk Süsserott [this message]
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=4A0DC997.9040604@suesserott.de \
--to=poststelle@suesserott.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newsletter@dirk.my1.cc \
/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).