On 10/28/07, pgeorges <[EMAIL PROTECTED]> wrote: > Ejner Borgbjerg a écrit : > > Excuse me for asking a curious - but for sure a naive - question. I > > did not follow this discussion previously ! > > What is the problem with making a fork of Scid and have that fork > > hosted by SF ? Wouldn't that solve your needs here ? > > > > > > > First I don't like "forks". If one day someone manages to continue Scid, > there is no interest in any fork for me. > Regarding another project at Sourceforge, what name to choose ? I don't > want to rename Scid to "xxxx" and change all occurences of Scid in > source code. This would make change tracking difficult. >
I see. If I had to start a fork project, I would probably refrain from renaming any source code. At least as long as there still was any meaning in diff-ing the source trees. But of course I agree with you that it would be much better to just work on the existing project. A pity if someone is blocking you out... :-( Ejner ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
