Gnus development mailing list
 help / color / mirror / Atom feed
From: Elias Oltmanns <eo@nebensachen.de>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: [Patch] Make tls.el support certificate verification
Date: Sat, 17 Nov 2007 00:07:31 +0100	[thread overview]
Message-ID: <877ikhlrgs.fsf@denkblock.local> (raw)
In-Reply-To: <v9ir414xzu.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> On Fri, Nov 16 2007, Elias Oltmanns wrote:
>
>> Well, I sent ChangeLog entries a week ago (see [1] and [2]) but nothing
>> has shown up in cvs yet.  
>
> Sorry for the delay, I didn't have a change do commit your changes
> during the past week (I'm not at home and I don't have a reasonable
> internet connection at the moment).

Alright.  Thanks for clarifying.

[...]
>> This is particularly annoying if the message actually contains a
>> ready made patch to fix a bug and all I'm asking for is to review
>> the patch and tell me what's wrong with it so it can be committed
>> eventually.  
>
> If you don't get responses, please feel free to remind us about the
> issue.  (Before your papers had been arrived, we couldn't install your
> patches.)

Yes, I realise that and that's why I had hoped for a more timely
response to my ChangeLog entries since I had posted them after papers
had been signed.  Of course, there always is a chance for unfortunate
coincidences, so, thanks for your explanation.

[...]
>> This makes me wonder whether I should generally send patches to the
>> emacs-devel list rather than the ding list even if they concern the
>> gnus trunk.  
>
> Now that the Gnus trunk is also in Emacs trunk you may send it
> emacs-devel in this case as well.  But please keep ding copied too.

Actually, I'd prefer the ding list myself since it has much lower
traffic than emacs-devel.

Regards,

Elias

  reply	other threads:[~2007-11-16 23:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-16 23:08 Elias Oltmanns
2007-09-24  7:12 ` Simon Josefsson
2007-09-24 16:27   ` Reiner Steib
2007-09-25 14:42     ` Simon Josefsson
2007-11-08 18:44       ` Elias Oltmanns
2007-11-08 19:52         ` Reiner Steib
2007-11-16 17:22           ` Elias Oltmanns
2007-11-16 22:38             ` Reiner Steib
2007-11-16 23:07               ` Elias Oltmanns [this message]
2007-11-24 21:31                 ` Reiner Steib
2007-11-25  0:35                   ` Elias Oltmanns
2007-11-25 14:18                     ` Reiner Steib
2007-11-26 14:47                       ` Simon Josefsson
2007-11-27 11:10                   ` Elias Oltmanns
2007-11-28 22:05                     ` Reiner Steib
2007-11-28 22:08                     ` Coding conventions (was: [Patch] Make tls.el support certificate verification) Reiner Steib

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877ikhlrgs.fsf@denkblock.local \
    --to=eo@nebensachen.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).