fineract-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vishwas Babu <vish...@confluxtechnologies.com>
Subject Re: Missing git history
Date Sat, 30 Jan 2016 07:32:26 GMT
Markus,

Git does an excellent job of recognizing renamed files. Merging forks with
the new package structure is a very straightforward process.

What is the issue with retaining the commit history ?

Regards,
Vishwas





On Sat, Jan 30, 2016 at 11:29 AM, <markus.geiss@live.de> wrote:

>
>
> Hey Vishwas,
>
>
> The repackeging led to a delete and add of all files anyways, so a simple
> fetch merge could cause more harm than the creation of a new fork and
> manually transfer made changes to the code that never where contributed
> back.
>
>
> In addition I'd suggest to do future code enhancements in a way that
> allows either a contribution back or keeps the forked base clean and
> mergable.
>
>
> Best,
>
>
> Markus
>
>
> .:: YAGNI likes a DRY KISS ::.
>
>
>
> From: Vishwas Babu
>
> Sent: Saturday, January 30, 02:46
>
> Subject: Missing git history
>
> To: dev@fineract.incubator.apache.org
>
>
>
> Hi,
>
>
> https://github.com/apache/incubator-fineract doesn't carry over the commit
>
> history from https://github.com/openMF/mifosx.
>
>
> Given that the MifosX platform has been around for a few years now,
>
> numerous organizations maintain multiple forks of the same . Without the
>
> commit history being carried over, upgrading these forks becomes an
>
> unnecessarily painful process.
>
>
> Also, the contribution history of around 78 volunteers to the original
>
> MifosX project is lost.
>
>
> Is there any reason for initializing fineract as a new git repository ?
>
>
> Regards,
>
> Vishwas
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message