Can we dont work with an assumption that upto some ver is on git and we start new repo on svn.
-- mohit On Thu, Nov 10, 2011 at 11:34 PM, Leo Neumeyer <[email protected]>wrote: > I don't know if it is useful but it doesn't hurt either and preserves some > history for the records, I mean just a dump of the commit log (git log). We > should also archive the entire git repo in svn and move on. I think history > should be hosted with the rest of the code. > > -leo > > On Thu, Nov 10, 2011 at 8:35 AM, Matthieu Morel <[email protected]> wrote: > > > On 11/10/11 5:05 PM, Leo Neumeyer wrote: > > > >> I propose just putting the commit history in a separate file so it stays > >> in > >> the repository, what do you think? > >> > >> Let's just do this soon so we can complete the move. > >> > >> In my opinion, a separate file with a list of commits would not be very > > useful. > > > > Considering that: > > 1. apparently we have to use svn for the master branch, and > > 2. we are working on a complete refactoring, > > I would suggest to simply forget the history for the migration of S4 0.4 > > to svn, so that we can make progress with this task. > > > > We have the full history until the migration in github already anyway, if > > needed. > > > > Matthieu > > > > > > -- > > Leo Neumeyer (@leoneu) >
