From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: egit-dev@eclipse.org, git@vger.kernel.org
Subject: Re: [EGIT PATCH] Rename org.spearce.egit -> org.eclipse.egit
Date: Fri, 19 Jun 2009 01:20:29 +0200 [thread overview]
Message-ID: <200906190120.29915.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <1245253576-13324-1-git-send-email-spearce@spearce.org>
Need an idea on how to proceed here. There is a problem related to updating
plugins here. We have renamed feature with one unrenamed plugin. How
to we avoid problem when switching from org.spearce to org.eclipse
One option is to release a v0.4.1 (which we should do anyway), which is the last
version from master before the split. For technical reasons this will be
a branch since the split occurred already.
That 0.4.1 feature should require jgit < 0.5. Then we jgit to v0.5 and
make org.eclipse.egit require jgit >= 0.5
Having two EGit features will be confusing. You get two of everything. E.g.
Team>Share will have two Git's to choose from, but you cannot tell which
is which.
That said, having both could be a feature, since it (didn't really try it), would
be possible to switch between new and old workspaces and get the plugin
configured for that workspace. The wierdness make me suggest we do
not do this. If we really want it we could choose to create a proxy plugin
for attaching old workspaces to the new plugins.
-- robin
next parent reply other threads:[~2009-06-18 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1245253576-13324-1-git-send-email-spearce@spearce.org>
2009-06-18 23:20 ` Robin Rosenberg [this message]
2009-06-18 23:24 ` [EGIT PATCH] Rename org.spearce.egit -> org.eclipse.egit Shawn O. Pearce
2009-06-19 8:47 ` [egit-dev] " Alex Blewitt
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=200906190120.29915.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=egit-dev@eclipse.org \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).