As of now I believe that repo is the test repo for the p2 migration. Although if you are seeing strangeness with it then it may indicate a problem encountered when they did the test migration to create the repo.
Tom
From: "Todorova, Katya" <[email protected]>
To: P2 developer discussions <[email protected]>
Date: 07/11/2011 06:36 AM
Subject: Re: [p2-dev] Pending patches in preparation to Git move
Guys,
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?
Thanks,
Katya
From: [email protected] [mailto:[email protected]] 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 <[email protected]>
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).
Later,
PW
--
Paul Webster
Hi floor. Make me a sammich! - GIR
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
