Re: Hello mc Maintainers! :)
I removed Egmond from Uhulinux, he doesn't work anymore for uhulinux according a mail I recived right after sending my previous one. * having a own repository where we have different branches for every distribution and one branch for a pure patchset. Then we can start to put all patches into the corresponding branch (e.g. I would put my ones into the debian branch). After that we can discuss every patch (there will be some different approaches of patch the same thing). and merge it into the main one. After we are done with every patch (of course except the ones which are distribution specific) we have a patchset for the CVS from upstream and can start to rediff them for the distributions needs. E.g. one distribution is using 4.6.2-pre1 and not a cvs snapshot then were will be a little work to rediff it, but this shoudl be quite easy. This guarantees that everybody uses the same patchset, that if there is a fix in one distribution for a error, this will be afterwards in every distribution. OK, that could work. Yes, I hope so. This is basically the same as your wiki idea only using a VCS instead. git would do the job quite good, but cvs will work, too, I guess. I am most familiar with cvs and svn, but maybe git would fit better. I am most familiar with svn and cvs, too but there are some things I really miss in svn ... I dislike the idea of branching there. git is quite new for me, too, but as I heard from different people it should be exactly what is needed here. I've got a comment on a blogpost from another Debian Developer. This site he mentioned on my Discussion page is worth to have a look on. http://www.der-winnie.de/posts/collab-maint_between_distributions__63__/discussion/ But I think that we should made this discussion visible for upstream. What about moving it to mc-devel? Yes, indeed. I've cc'ed it. Is everybody here subscribed to this list? If yes we can use this list for a first start to discuss everything. Greetings Winnie -- .''`. Patrick Winnertz [EMAIL PROTECTED] : :' : GNU/Linux Debian Developer `. `'` http://www.der-winnie.de http://people.skolelinux.org/~winnie `- Debian - when you have better things to do than fixing systems signature.asc Description: This is a digitally signed message part. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Hello mc Maintainers! :)
On Fri, 2008-03-07 at 17:23 +0100, Patrick Winnertz wrote: This is basically the same as your wiki idea only using a VCS instead. git would do the job quite good, but cvs will work, too, I guess. I am most familiar with cvs and svn, but maybe git would fit better. I am most familiar with svn and cvs, too but there are some things I really miss in svn ... I dislike the idea of branching there. git is quite new for me, too, but as I heard from different people it should be exactly what is needed here. I can set up a git mirror on http://repo.or.cz/ and keep it updated from the cron script. I'm doing it for another project already. The greatest thing about git (especially when used with StGIT frontend) is that is allows working on several patches at once. Complete switching to git would be great, but it would need getting rid of changelogs and relying on the commit messages for the history. That's something only the maintainers can decide. But just having a git mirror would help those who cannot stand working in CVS after trying git or another modern version control system. -- Regards, Pavel Roskin ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Hello mc Maintainers! :)
On Friday 07 March 2008 19:55:10 Pavel Roskin wrote: On Fri, 2008-03-07 at 17:23 +0100, Patrick Winnertz wrote: This is basically the same as your wiki idea only using a VCS instead. git would do the job quite good, but cvs will work, too, I guess. I am most familiar with cvs and svn, but maybe git would fit better. I am most familiar with svn and cvs, too but there are some things I really miss in svn ... I dislike the idea of branching there. git is quite new for me, too, but as I heard from different people it should be exactly what is needed here. I can set up a git mirror on http://repo.or.cz/ and keep it updated from the cron script. I'm doing it for another project already. This would rock.. Please do. Thanks in advance Greetings Winnie -- .''`. Patrick Winnertz [EMAIL PROTECTED] : :' : GNU/Linux Debian Developer `. `'` http://www.der-winnie.de http://people.skolelinux.org/~winnie `- Debian - when you have better things to do than fixing systems signature.asc Description: This is a digitally signed message part. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Hello mc Maintainers! :)
On Fri, 2008-03-07 at 21:50 +0100, Patrick Winnertz wrote: On Friday 07 March 2008 19:55:10 Pavel Roskin wrote: On Fri, 2008-03-07 at 17:23 +0100, Patrick Winnertz wrote: This is basically the same as your wiki idea only using a VCS instead. git would do the job quite good, but cvs will work, too, I guess. I am most familiar with cvs and svn, but maybe git would fit better. I am most familiar with svn and cvs, too but there are some things I really miss in svn ... I dislike the idea of branching there. git is quite new for me, too, but as I heard from different people it should be exactly what is needed here. I can set up a git mirror on http://repo.or.cz/ and keep it updated from the cron script. I'm doing it for another project already. This would rock.. Please do. It took me some time to make a list of all committers. I never expected it to be so long - 105 committers! I could not recover names of davidsa, gertd and martin because they never committed any ChangeLog entries. The final (hopefully) import is in progress. I hope it will complete overnight. The project patch is http://repo.or.cz/w/mc.git If something is wrong, please let me know. -- Regards, Pavel Roskin ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
