From: Hadron <hadronquark@googlemail.com>
Cc: help-gnu-emacs@gnu.org, Hadron <hadronquark@gmail.com>
Subject: Re: ediff in RCS
Date: Mon, 18 Jun 2007 11:00:12 +0200 [thread overview]
Message-ID: <87d4zt7i3n.fsf@gmail.com> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICIEIJDNAA.drew.adams@oracle.com> (Drew Adams's message of "Sun, 17 Jun 2007 17:38:40 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
>> Possibly a good idea to comment them as such?
>
> Yes, perhaps. But I have no idea that there are any problems (though your
> report might be related). I haven't used change control much since I started
> using Windows ;-). I just haven't felt like installing it.
>
>> The copyright indicates
>> 2007 so I assumed the code was maintained and working :(
>
> Bad assumption.
Yup - I wasted a lot of time.
Easy way to address it of course and take "assumption" out of the
equation is to just add a "old and not maintained and unlikely to work"
comment :-;
>
> Even a recent change-log entry (though there are none in these files)
> wouldn't necessarily mean that the library was working on that log date. The
> change could just be something as simple as updating the address of the FSF
> in the free-software declaration. Checking for a recent change-log entry and
> reading what it says can help, but again, there are no guarantees.
>
> Sorry for any inconvenience.
>
No worries - it was educational.
--
next prev parent reply other threads:[~2007-06-18 9:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2307.1182121306.32220.help-gnu-emacs@gnu.org>
2007-06-17 23:14 ` ediff in RCS Hadron
2007-06-18 0:38 ` Drew Adams
2007-06-18 9:00 ` Hadron [this message]
2007-06-18 20:10 ` Andreas Röhler
2007-06-24 16:39 ` Tom Tromey
[not found] <mailman.2312.1182127247.32220.help-gnu-emacs@gnu.org>
2007-06-18 17:33 ` don provan
2007-06-17 22:12 Hadron
2007-06-17 23:00 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d4zt7i3n.fsf@gmail.com \
--to=hadronquark@googlemail.com \
--cc=hadronquark@gmail.com \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).