From: Dave Love <fx@gnu.org>
Subject: Re: Commits to GNUS-NEWS
Date: Thu, 01 Dec 2005 23:42:29 +0000 [thread overview]
Message-ID: <rzqek4wcrkq.fsf@loveshack> (raw)
In-Reply-To: <v9zmnk373o.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 01 Dec 2005 21:17:15 +0100")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> Thanks for fixing these. Alas, GNUS-NEWS is generated from
> `texi/gnus-news.texi'.
Yes, sorry, I was already told. I checked in the makefile to see if
it was built, but forgot I had my makefile and, I think, hadn't
reconfigured. :-(
> I've merged your changes into
> `texi/gnus-news.texi' and `texi/gnus-news.el' and will commit them
> tomorrow (when I'll have a better connection).
I already did that.
> BTW, maintenance issues like this are (or at least should be)
> documented in `texi/gnus-coding.texi' (work in progress).
Ah, OK. I guess it's better to send patches for something I'm not
involved in.
next prev parent reply other threads:[~2005-12-01 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Ehqgj-0003M7-00@quimby.gnus.org>
2005-12-01 20:17 ` Reiner Steib
2005-12-01 23:42 ` Dave Love [this message]
2005-12-02 18:25 ` 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=rzqek4wcrkq.fsf@loveshack \
--to=fx@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).