OK so unless we have nothing better to do but try to preserve the history of maintenance of openstack-swift between the time it was written, the few minor changes, and boatload of maintenance, I'd suggest we just merge the following.
openstack-swift out of labs https://github.com/jclouds/jclouds/pull/563 - master https://github.com/jclouds/jclouds/pull/564 - 1.8.x -A On Wed, Oct 8, 2014 at 7:38 AM, Adrian Cole <adrian.f.c...@gmail.com> wrote: > Wires crossed! > > Ok. I will raise a source import pull request for openstack-swift and > friends. I suppose I could simultaneously for 1.8.x just wait until we are > ready to merge that. > > -A > > On Oct 8, 2014 7:31 AM, "Ignasi Barrera" <ignasi.barr...@gmail.com> wrote: >> >> The same happens to chef. I've tried to find a way to keep history, >> but I haven't found any. Take into account that moving to the main >> repo also implies a "restructure" of the project. In the case of Chef, >> the "core" folder is moved to "apis", and the "enterprisechef" one to >> "providers". >> >> On 8 October 2014 16:21, Andrew Phillips <aphill...@qrmedia.com> wrote: >> >> While this wouldn't retain history, we can cite the >> >> jclouds-labs-openstack repo for history. Other ideas welcome. >> > >> > >> > Sounds good to me - what are we doing with jclouds-chef, which is also >> > undergoing a similar merge at this time? >> > >> > Would filter-branch [1] help in preserving history in some way? Could we >> > "convert" the repo to a branch on master and submit a PR to merge that? >> > >> > ap >> > >> > [1] http://git-scm.com/docs/git-filter-branch
