From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: Re: what the heck happened to gnus-spec ?!
Date: 08 Dec 1999 19:51:41 +0100 [thread overview]
Message-ID: <by3dtd1d1e.fsf@bolzano.math.ethz.ch> (raw)
In-Reply-To: Didier Verna's message of "Wed, 08 Dec 1999 17:43:35 GMT"
Didier Verna <didier@epita.fr> writes:
> The balloon-help property format spec has been broken. Here's a diff
> between the latest working version I have, and the latest CVS version. I
> don't understand these modifications. If they were intentional, they should
> /at least/ have been ChangeLog'ed, and commented in the documentation. But
> those modifications look wrong anyway.
>
> Does anybody remember doing this ?
If you have write access to the CVS you can use 'cvs annotate' to find
the guilty party.
Jan
next prev parent reply other threads:[~1999-12-08 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-08 17:50 Didier Verna
1999-12-08 17:54 ` Hrvoje Niksic
1999-12-08 18:51 ` Jan Vroonhof [this message]
1999-12-08 19:29 ` Didier Verna
1999-12-08 19:22 ` Toby Speight
2000-04-21 19:25 ` Lars Magne Ingebrigtsen
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=by3dtd1d1e.fsf@bolzano.math.ethz.ch \
--to=vroonhof@math.ethz.ch \
/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).