From: "Tor Arne Vestbø" <torarnv@gmail.com>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>, git@vger.kernel.org
Subject: Re: [EGIT PATCH] Fix invalid menubar and toolbar entries in plugin.xml
Date: Thu, 14 Aug 2008 21:13:51 +0200 [thread overview]
Message-ID: <48A483EF.10508@gmail.com> (raw)
In-Reply-To: <200808141942.55448.robin.rosenberg.lists@dewire.com>
Robin Rosenberg wrote:
>>> The menu entry was not used, and was causing an extra
>>> empty space in the menu bar.
>
> When I applied this patch the Git menu disappeared. (3.3)
Ah, I see. It appears the menu was used, but because it had the wrong
path ('org.spearce.egit.ui.gitmenu' instead of 'additions') the four
entries did not show up in 3.4.
Either way I suggest the patch is still valid, because it removes
the Git menu from the menu bar. This is consistent with what other
platform plugins do, ie. not populating the main menu bar with plugin
specific entries, but instead using sub menus, context menus and views.
In the long run we should probably also move the global toolbar entries
to the synchronize view, when I get the chance to look at implementing
that.
Tor Arne
next prev parent reply other threads:[~2008-08-14 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 19:07 [PATCH] Fix invalid menubar and toolbar entries in plugin.xml Tor Arne Vestbø
2008-08-14 5:47 ` [EGIT PATCH] " Robin Rosenberg
2008-08-14 17:42 ` Robin Rosenberg
2008-08-14 19:13 ` Tor Arne Vestbø [this message]
2008-08-14 20:42 ` Robin Rosenberg
2008-08-14 20:45 ` [EGIT PATCH] Hide the Git menu and toolbars by default and fix the path of the Git menu Robin Rosenberg
2008-08-14 21:43 ` [EGIT PATCH] Fix invalid menubar and toolbar entries in plugin.xml Tor Arne Vestbø
2008-08-14 22:07 ` [EGIT PATCH v2] " Tor Arne Vestbø
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=48A483EF.10508@gmail.com \
--to=torarnv@gmail.com \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.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).