X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=tWA4tvwJZm/O22998iSPGmGH0zB4FVTSA3b6bPp3dUg=; b=A9IKS9ya6gWtAe5Xg02sg8N+c4gjdH65WISdO1/J2tHhJ9UQiM2wIzCoWdPyxt5D9c JJU41goOADFIPPFLAkLkia6lOnx8B81LUC9ZaLrVlUYWqE3KLSZrD1v7mAY9fFNmJx1B Aob6kCDiWCphZ/JW7ACyzPJWqZ2FmQe1l86r6T5F7ufiS+BY4lhW39wdiix2kvJU6Qq8 3IS5mbT4qTo5cfnHMcwpW+opaz2/jKPD3DT1F8FUKynb8/EI3JJneoru37A+LdBBxLH5 VjvpFesaiY9vsF9GJXOj4oVkQp2LAJGufbQ34TB/r7JEAO5o/ak7LysJrmLTYgJ1RApt HpQg== MIME-Version: 1.0 X-Received: by 10.194.58.199 with SMTP id t7mr54129574wjq.45.1440537803706; Tue, 25 Aug 2015 14:23:23 -0700 (PDT) In-Reply-To: References: <55D8D8B8 DOT 7050907 AT jump-ing DOT de> <55D9BDC7 DOT 4000608 AT jump-ing DOT de> Date: Tue, 25 Aug 2015 13:23:23 -0800 Message-ID: Subject: Re: [geda-user] Antifork From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, Aug 23, 2015 at 6:29 PM, wrote: > > > On Sun, 23 Aug 2015, Britton Kerin (britton DOT kerin AT gmail DOT com) [via > geda-user AT delorie DOT com] wrote: > >> >> Unfortunately no one is going to be nearly so well positioned to merge >> your >> stuff as you are. Relatively, it will be painfully inefficient for >> them and they >> will feel it as they work. > > > Unfortunately no one is as unmotivated to invest time in this as I am. This > won't happen, sorry. I take it you acknowledge that no one can do it as easily as you. But I guess you also feel that since others don't want to bother much, there's no reason you should bother or use build/vcs you dislike. Suppose someone else did do the work to merge it this time, would you feel then feel more or less inclined to use common build system etc. and generally design-for-mergability in the future? >> The reason everyone is so worked up about this particular fork is that it >> has >> the most interesting new features in a long time. I'll take another run >> at >> testing it soon. But I agree with others that to give up on merging it is >> very sad, especially when the problems are things like VCS and build >> system, >> that don't even have anything to do with the core functionality. > > I didn't give up on the merge: I never intended to push it in the first > place. It's totally indifferent for me as I am not an user of the mainline > pcb. If anyone decides to merge whichever part he likes, that's fine. If he > has questions about why/how some parts are implemented, I'm happy to > explain. > > Forks may have different purposes. Some forks are created by the author in > hope that he can merge it back to mainline, some are not. I guess if you're correct that nothing worthwhile to you will happen in mainline pcb ever again, you have the right approach. Otherwise its a loss for you as well as everyone else. My fantasy when I heard about ruby scripting in pcb was that perhaps Stefan's router might someday see the light of day afterall. Oh well Britton