🚀 go-pugleaf

Uday S Reddy <uDOTsDOTreddy@cs.bham.ac.uk> writes:
> This is not helpful.  I have tried the "two patches you submitted",
> found problems, and sent you back the corrections.  Did you apply them
> and test them?  If you didn't do so, the further exchange didn't make
> any contribution.  In fact, it wasn't clear if we were even talking
> about the same things any more.

I didn't see the corrections you sent me and didn't see you asking me
to test them. The only "patch" I saw was basically the same one that I
suggested except that:
- You added the additional line which I don't think is necessary
      -	(command (process-command process)))
      +	(process-command (process-command process)))
- You left out the other patched line that I have mentioned MULTIPLE
  TIMES -- adding a comma before ,wait
  IT WILL CRASH WITHOUT THAT CHANGE.

> (My apologies for having misremembered that I committed the changes to
> launchpad.  I posted the patches here and was waiting to hear from
> you.  I have now uploaded my version to launchpad so that you can test
> it properly.)

As I mentioned before, in addition to not knowing that you had committed
the patcheds launchpad, I was using the wrong launchpad site based on
your posting from November
     From: Uday S Reddy <uDOTsDOTreddy@cs.bham.ac.uk>
     Subject: Towards VM 8.1
     Newsgroups: gnu.emacs.vm.info
     Date: Tue, 17 Nov 2009 17:46:38 +0000
     Organization: Janet Usenet Reading Service.

     Folks, bad news and good news.

     I haven't gotten a response from Rob F to my email messages.  He may yet
     come back, but we need to proceed on the assumption that he will not be
     available for some time.

     At the same time, I have been able to create a branch at Launchpad for
     VM 8.1.  The URL is

       http://bazaar.launchpad.net/~reddyuday/viewmail/8.1

As a newbie to launchpad, I had no idea that there was another VM
launchpad site at:
      http://bazaar.launchpad.net/~vm/vm/trunk/files/head%3A/lisp/

Personally, I find launchpad awkward and confusing but I will try to use
it if that is what the team is using.

Anyway let's stop this back-and-forth and get back to good coding. I
think there is enough blame to go around and we can each take away
lessons for the future from this interchange.