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

List:       kde-scm-interest
Subject:    Re: [Kde-scm-interest] Migration of KDESDK to git
From:       "Friedrich W. H. Kossebau" <kossebau () kde ! org>
Date:       2012-06-01 16:13:11
Message-ID: 3604957.y5PGpRmFnf () klux ! site
[Download RAW message or body]

Am Freitag, 1. Juni 2012, 17:54:42 schrieb Ian Monroe:
> On Fri, Jun 1, 2012 at 1:58 PM, Friedrich W. H. Kossebau
> 
> <kossebau@kde.org> wrote:
> > Am Mittwoch, 30. Mai 2012, 12:41:13 schrieb Josef Weidendorfer:
> >> How to handle kdesdk/debian?
> 
> well they will have to redo it all anyways won't they? With the build
> system changes and possibly new tarballs if you are doing that.

The question about kdesdk/debian was more how to handle the history here. 
Currently any non-submodule files and directories (current or previous) in the 
toplevel directory will be lost/unaccessible in git after the migration, 
unless they has been moved into one of the submodules before, as the repos 
will be created only based on the content in there.

So the question is: is the history of the debian folder (does not exist in 
trunk anymore) important, or could it simply be lost/unaccessible in the git 
repo(s)?

> >> Do we want the trinity stuff in the git repos?
> 
> Keep it, ignore it, not sure it matters. Normally in git you should be
> afraid of history that is adding junk, since its impossible to delete
> history without destroying all tracing. But since Trinity isn't part
> of the history of the 'mainline' code, you could decide 5 years from
> now to clean up the git repo by deleting the branch and it would be
> fine.

Sure. It's more a matter of being consistent with the other modules :)

Friedrich
_______________________________________________
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]