All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] git-gui: Add a special diff popup menu for submodules
Date: Sat, 23 Jan 2010 14:57:55 -0800	[thread overview]
Message-ID: <20100123225755.GF12679@spearce.org> (raw)
In-Reply-To: <4B3F7B49.2030100@web.de>

Jens Lehmann <Jens.Lehmann@web.de> wrote:
> To make it easier for users to deal with submodules, a special diff popup
> menu has been added for submodules. The "Show Less Context" and "Show More
> Context" entries have been removed, as they don't make any sense for a
> submodule summary. Four new entries are added to the top of the popup menu
> to gain access to more detailed information about the changes in a
> submodule than the plain summary does offer. These are:
> - "Visualize These Changes In The Submodule"
>   starts gitk showing the selected commit range
> - "Visualize These Changes In The Submodule"
>   starts gitk showing the whole submodule history of the current branch
> - "Visualize All Branch History In The Submodule"
>   starts gitk --all in the submodule
> - "Start git gui In The Submodule"
>   guess what :-)
> 
> Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
> ---
>  git-gui/git-gui.sh |  127 +++++++++++++++++++++++++++++++++++++++++++++-------
>  1 files changed, 110 insertions(+), 17 deletions(-)

Thanks, applied.

-- 
Shawn.

      reply	other threads:[~2010-01-23 22:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-02 16:57 [PATCH 0/2] git-gui: Add a special diff popup menu for submodules Jens Lehmann
2010-01-02 16:58 ` [PATCH 1/2] git-gui: Unstaging a partly staged entry didn't update file_states correctly Jens Lehmann
2010-01-02 16:58 ` [PATCH 2/2] git-gui: Add a special diff popup menu for submodules Jens Lehmann
2010-01-23 22:57   ` Shawn O. Pearce [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=20100123225755.GF12679@spearce.org \
    --to=spearce@spearce.org \
    --cc=Jens.Lehmann@web.de \
    --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.