Nonsense
Epicea has nothing to do with RB goals.
Epicea is to replace the changes file because we want a better change file
and separate
the code management from the version recording (micro commits).
Source code could be managed in a separate database and microchanges
can be managed to recover c
On Wed, May 3, 2017 at 5:22 AM, Denis Kudriashov
wrote:
>
> 2017-04-26 11:19 GMT+02:00 Peter Uhnak :
>
>> Hi,
>>
>> I'm under the impression that Epicea is supposed to replace RB
>> refactorings at some point.
>>
>
> I think it was never the goal and not supposed to happen. Epicea is only
> chang
2017-04-26 11:19 GMT+02:00 Peter Uhnak :
> Hi,
>
> I'm under the impression that Epicea is supposed to replace RB
> refactorings at some point.
>
I think it was never the goal and not supposed to happen. Epicea is only
changes logger. Maybe Martin will correct me.
>
> If that is true, is it cur
anyone?
On Wed, Apr 26, 2017 at 11:19:07AM +0200, Peter Uhnak wrote:
> Hi,
>
> I'm under the impression that Epicea is supposed to replace RB refactorings
> at some point.
>
> If that is true, is it currently possible to build refactorings by hand?
>
> For example in RB I often do:
>
> ```
>
