[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-scm-interest
Subject:    Re: [Kde-scm-interest] Sysadmin advice regarding Monolithic vs
From:       Ian Monroe <ian () monroe ! nu>
Date:       2010-09-08 13:26:46
Message-ID: AANLkTinYqp43ajx2tOCm1Eyh7gXrm9HiCTp8x1Zs23y6 () mail ! gmail ! com
[Download RAW message or body]

On Wed, Sep 8, 2010 at 5:59 AM, Torgny Nyblom <kde@nyblom.org> wrote:
> On Tue, 7 Sep 2010 15:03:39 -0500
> Ian Monroe <ian@monroe.nu> wrote:
>
> [...]
>> AFAIK, its impossible to have svn2git rules for a monolithic repo like
>> KDE Multimedia with submodules like Dragon Player produce complete
>> history. So I think we are misunderstanding each other?
>
> Why? What kind of change cannot svn2git handle?

Dragon Player had a standard story: started in playground, moved to
kdereview, moved to kdemultimedia.

With monolithic modules, svn2git is not able to save the history from
before it moved to kdemultimedia.

>> It's likely possible to create a complete history (meaning, a separate
>> git commit for every SVN commit) for Dragon Player once its treated as
>> a separate repo by svn2git. And therefore Torgny Nyblom's concerns
>> about splitting making history-completeness worse are misplaced.
>
> Why would this be easier? Use these rules in the above context but with
> a prefix if necessary.

That doesn't work, I've tried and its a known thing.

Ian
_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
[prev in list] [next in list] [prev in thread] [next in thread]