BTW, you can have a look at the commit history and the history of the
files in the main repo and the history of chef specific files such as
the ChefApi)

On 8 October 2014 18:04, Ignasi Barrera <ignasi.barr...@gmail.com> wrote:
> It seems possible. I've just merged jclouds-chef/core and
> jclouds-chef/enterprise to jclouds/apis/core and
> jclouds/providers/enterprisechef. See it at:
> https://github.com/nacx/jclouds/tree/jclouds-chef-merge
>
> I'm writing a page on the wiki with the steps I followed. If we all
> agree, we could discuss the procedure and use it.
> I'll share the page once I've finished it.
>
> On 8 October 2014 18:01, Jeremy Daggett <jeremy.dagg...@rackspace.com> wrote:
>> I looked into filter-branch a while back just for this purpose.! If we
>> could retain history, that would be ideal. Let me get my SCM hat on and
>> take a look.
>>
>> /jd
>>
>> On 10/8/14, 7:43 AM, "Ignasi Barrera" <n...@apache.org> wrote:
>>
>>>Actually, I'm still trying to keep the history with a couple more
>>>tests. If I can find a way, I'll post a howto on the wiki.
>>>
>>>On 8 October 2014 16:30, 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
>>

Reply via email to