[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Repository migration to Git - Today

Andrew and I looked through these fake commits. Most of them involve cherry-picking a commit that added a very large file (a content.jar in the p2 tests bundle). I suspect this is an attempt by cvs2svn to optimize the repository space usage by adding that same commit on all branches rather than duplicating it. In any case, it doesn't look like there is an easy fix for this, so I think we will just need to live with it. The main symptom is that many version tags are on little branches off the trunk rather than directly on the trunk. This makes the version history a bit more cluttered but I don't think it impacts us in our daily work.

John

On Wed, Jul 20, 2011 at 10:37 AM, Andrew Niefer <aniefer@xxxxxxxxxx> wrote:
That script has already been run against p2, framework and bundles repositories.  While it is able to fix the majority of manufactured commits, it is not able to remove them all.

There are some cases where commits must be cherry picked from elsewhere in the tree, this is likely caused by multiple projects receiving the same tag but at different points in time with several commits between tagging.  Or also by moving a tag in cvs.  The cleanup script is not able to fix these, and I'm not even sure how to fix them manually.

I talked to John briefly and he is seeing many more of these commits than I am, I will follow up with him to make sure everything is ok.

-Andrew


From: Thomas Watson <tjwatson@xxxxxxxxxx>
To:
P2 developer discussions <p2-dev@xxxxxxxxxxx>
Date: 07/20/2011 09:53 AM
Subject:
Re: [p2-dev] Repository migration to Git - Today
Sent by: p2-dev-bounces@xxxxxxxxxxx





I noticed some of these fake commits in the rt.equinox.framework and rt.equinox.bundles repositories. Now that we have been using these repositories for over a week is it too late to fix them also?

Tom



Inactive hide details for John Arthorne ---07/20/2011 08:42:47 AM---It looks like the conversion isn't complete. This repositorJohn Arthorne ---07/20/2011 08:42:47 AM---It looks like the conversion isn't complete. This repository is full of fake commits inserted by cvs2svn. There is a script to

From:

John Arthorne <arthorne.eclipse@xxxxxxxxx>

To:

P2 developer discussions <p2-dev@xxxxxxxxxxx>

Date:

07/20/2011 08:42 AM

Subject:

Re: [p2-dev] Repository migration to Git - Today





It looks like the conversion isn't complete. This repository is full of fake commits inserted by cvs2svn. There is a script to fix that up. You might want to double-check with Paul but I think it is this one:


http://wiki.eclipse.org/Platform-releng/Juno_Git_Migration_Recipe#Move_tags_into_place

John


On Tue, Jul 19, 2011 at 5:47 PM, Andrew Niefer <
aniefer@xxxxxxxxxx> wrote:
The p2 cvs repository has now been converted to git.

Read only access through

git://
git.eclipse.org/gitroot/equinox/rt.equinox.p2.git
Write access through
ssh://
git.eclipse.org/gitroot/equinox/rt.equinox.p2.git

I have updated the map files in the releng project so that tonight's N-Build will be built from git.


Please see
http://wiki.eclipse.org/Git#Committers_new_to_Git for information on how to get started with git.

-Andrew

From: DJ Houghton/Ottawa/IBM@IBMCA
To: P2 developer discussions <p2-dev@xxxxxxxxxxx>
Date: 07/19/2011 01:39 PM
Subject: [p2-dev] Repository migration to Git - Today
Sent by: p2-dev-bounces@xxxxxxxxxxx







As discussed in the Equinox call last week, we are going to migrate the p2 repository to git this afternoon.
Please refrain from releasing code to the CVS repo until we send a message that the migration is complete.
Once the migration is complete the CVS repo will be considered read-only and builds, etc will be done from the new git repo.

Related/similar messages about the conversion of the rest of the Equinox repositories can be found in the equinox-dev mailing list archives:

http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg06891.html
http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg06896.html


Thanks.
_______________________________________________
p2-dev mailing list

p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev



_______________________________________________
p2-dev mailing list

p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/p2-dev

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev



_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev