Re: [Engine-devel] New oVirt GIT Repo Request

Hi, a suggestion for the plan: you could use git filter-branch with the --subdirectory-filter option for creating the repos at step 1. That way it will keep commit history of the files being moved in the new repos.

Paulo de Rezende Pinatti Staff Software Engineer IBM Linux Technology Center On 02/10/2012 12:42 PM, Keith Robertson wrote: > All, > > I would like to move some of the oVirt tools into their own GIT repos > so that they are easier to manage/maintain. In particular, I would > like to move the ovirt-log-collector, ovirt-iso-uploader, and > ovirt-image-uploader each into their own GIT repos. > > The Plan: > Step 1: Create naked GIT repos on oVirt.org for the 3 tools. > Step 2: Link git repos to gerrit. > Step 3: Populate naked GIT repos with source and build standalone > spec files for each. > Step 4: In one patch do both a) and b)... > a) Update oVirt manager GIT repo by removing tool source. > b) Update oVirt manager GIT repo such that spec has dependencies on > 3 new RPMs. > > Optional: > - These three tools share some python classes that are very similar. > I would like to create a GIT repo (perhaps ovirt-tools-common) to > contain these classes so that a fix in one place will fix the issue > everywhere. Perhaps we can also create a naked GIT repo for these > common classes while addressing the primary concerns above. > > Please comment, > Keith Robertson > _______________________________________________ > Arch mailing list > Arch(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/arch >