[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Pending patches in preparation to Git move



Is git.eclipse.org/gitroot/equinox/rt.equinox.p2.git supposed to be ready to use?


I tried cloning it and the operation seems to finish successfully but afterwards most of the projects (when imported in Eclipse) don’t compile properly.

For example p2.repository doesn’t see some of the exported packages by p2.core.


Any idea what’s wrong?





From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent: jeudi 7 juillet 2011 14:13
To: P2 developer discussions
Subject: Re: [p2-dev] Pending patches in preparation to Git move


I checked and the patches provided for these projects just apply fine!

Thx Paul, this saves quite some pain :)


On 2011-07-07, at 12:41 PM, Pascal Rapicault wrote:

Ok great. I'll try with the test repo that Kim had created and will report.

On 2011-07-07, at 12:23 PM, Paul Webster wrote:

On Thu, Jul 7, 2011 at 5:35 AM, Pascal Rapicault <pascal@xxxxxxxxxxxx> wrote:

In preparation for the move of p2 to a git repo (see Tom's mail from yesterday), I have been thinking about releasing large pending patches into separate branches in CVS so that they are automatically carried over into the new git repo, and thus saves the author some nightmare related to dealing with reapplying the patch. What do you think about this?

Once your git repo is online and the projects imported into your workspace, the patches *should* apply from within eclipse just as before.

If you commit them to CVS in a branch for the effected projects,  the tool we use to convert cvs2git creates a "delete commit" at the base of the branch to get rid of anything not tagged and branched from CVS.  This could make a merge on the git side painful, and might force you to cherrypick your commit across (just an inconvenience, I know).


Paul Webster
Hi floor.  Make me a sammich! - GIR
p2-dev mailing list