Re: Eclipse-compatible :extssh: method...

[Derek Robert Price]

Deven T. Corzine wrote:

> While I might agree that "extssh" is a strange choice for a new method, 
> and it's not as generic as one might like, it is what it is.  That's what 
> Eclipse is already using, and it's out of my control.  Feel free to take 
> it up with the Eclipse developers.  Maybe you can convince them to do 
> things differently.  Don't put me in the middle of that discussion.
>
> I was only looking for interoperability between command-line CVS and the 
> implementation in Eclipse.  Patching CVS to understand the "extssh" method 
> that Eclipse uses was trivial.  Making "extssh" an alias for the "ext" 
> method would have been even more trivial, but then I'd need CVS_RSH set.

Well, they probably should have talked to us.

> > Don't forget cvs.texinfo documentation and test cases in sanity.sh.  
> > See the HACKING file in the top level of the CVS source distribution for
> > more on what is required for patch acceptance.
> >    
>
> Do you require every patch author to embark on a quest for acceptance 
> before you integrate the patches?  That's a good way to discourage people 
> from even sending the patch in the first place.

No, just most of them.  With really vital stuff I sometimes find the 
time to code that sort of thing myself.

> The patch I sent was trivial.  I offered it to you because I've heard many 
> complaints from open-source authors about patches that get created and 
> never submitted back to the author.  I've done my part -- I made a clean 
> patch and offered it to you for incorporation into the main distribution.  

[Remainder of rant clipped]

I really didn't mean to offend, it is simply that you are not the only 
person with demands on your time.

There are only a few active CVS developers and there are lots of 
features people would like to see and lots of patch submissions.  I know 
I usually don't have time to deal with all of them and, as you would 
know if you had read the HACKING file, it is pretty near pointless and 
generally self-defeating to commit new features to the tree without 
documentation and regression tests.  The new features without tests and 
docs usually quickly start developing bugs and fall into disuse.

I'm also very sorry to disappoint you.  We really do try our best to 
satisfy the CVS user commmunity, but there are limits on our time.  If 
you can't provide a complete patch, perhaps you would care to provide 
funding?

If it is any consolation, I am working on a patch to simplify the 
addition of tests and cvs.texinfo is fairly straightforward in the first 
place.

Again, sorry to disappoint.

Derek

--
               *8^)

Email: derek@ximbiot.com

Get CVS support at <http://ximbiot.com>!
--
... one of the main causes of the fall of the Roman Empire was that, 
lacking zero, they had no way to indicate successful termination of their C
programs.

        - Robert Firth