I usually use https://github.com/git/git/tree/master/contrib/subtree
for this kind of things, it's starting to be a bit old but it work
well. For example I used it when moving deprecated platform modules to
their own repository on contrib like
https://github.com/xwiki-contrib/xwiki-platform-wiki-manager.

On Mon, Mar 9, 2015 at 3:57 PM, Sergiu Dumitriu <[email protected]> wrote:
> That is doable, in two ways:
>
> 1. Merge xwiki-enterprise into xwiki-platform, move the modules we want
> to keep in their new location, delete the modules we don't need anymore.
> This requires planning where every module goes in advance, and fixes
> everything at once.
>
> 2. Extract each module that we want to keep in a separate git
> repository, using https://gist.github.com/sdumitriu/1993357 (I need to
> update this with a better version), and merge it into xwiki-platform.
> This lets us handle each module at a time, but extracting a module takes
> a while.
>
> On 03/09/2015 08:56 AM, Ecaterina Moraru (Valica) wrote:
>> Just some mentions about these removes/moves:
>> - We moved before things from XE to Platform. It's a pain if you want to
>> 'blame' the source and in the JIRA issue we don't have a link from where
>> the page was moved from. Tracking the history for a moved page is difficult
>> and a comment stating where the location was is useful.
>> - What will happen with the history if we remove the XE repository?
>>
>> Although the history + the blame use case might not be interesting for
>> everyone, myself I'm using it often to understand the initial purpose of
>> the feature, to determine if it's a regression, to know which person to
>> contact, etc.
>>
>> Do we have a strategy for keeping the history somehow?
>
> --
> Sergiu Dumitriu
> http://purl.org/net/sergiu
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs



-- 
Thomas Mortagne
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to