From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: [COMMIT] Fix for the enable-multibyte-characters problem
Date: 29 Sep 1999 20:18:45 +0200 [thread overview]
Message-ID: <m3so3x37ju.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <kh0u2odzkh9.fsf@abuffer.stanford.edu>
Matt Pharr <mmp@graphics.stanford.edu> writes:
> However, no changes have appeared in cvs-land--I can do stuff like
> the following to my heart's content with no results:
Huh, yes --
[larsi@quimbies ~/pgnus/lisp]$ cvs diff
? Makefile
cvs server: Diffing .
[larsi@quimbies ~/pgnus/lisp]$
Which means that cvs thinks that there are no differences between my
version and the one in the repository, right?
And I know that people have been checking stuff in. I'll have a peek
at the CVS files...
bash-2.03# ls -lt | head
total 19950
-r--r--r-- 1 cvs cvs 1081582 Sep 29 11:44 ChangeLog,v
-r--r--r-- 1 cvs cvs 31096 Sep 29 11:44 mm-util.el,v
-r--r--r-- 1 cvs cvs 21434 Sep 29 11:44 mm-bodies.el,v
-r--r--r-- 1 cvs cvs 15556 Sep 29 11:44 lpath.el,v
-r--r--r-- 1 cvs cvs 155841 Sep 29 11:44 gnus-start.el,v
-r--r--r-- 1 cvs cvs 17082 Sep 29 11:44 binhex.el,v
-r--r--r-- 1 cvs cvs 8655 Sep 28 02:59 rfc1843.el,v
-r--r--r-- 1 cvs cvs 17034 Sep 28 02:59 mm-uu.el,v
-r--r--r-- 1 cvs cvs 339007 Sep 28 02:59 gnus-art.el,v
These have newer timestamps than the files in my gnus/lisp directory.
So what's going on?
`C-x v =' says
No changes to /usr/home/larsi/pgnus/lisp/rfc2231.el since latest version
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-09-29 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-29 9:44 Didier Verna
1999-09-29 17:38 ` Matt Pharr
1999-09-29 18:18 ` Lars Magne Ingebrigtsen [this message]
1999-09-29 19:12 ` Sudish Joseph
1999-09-29 19:16 ` David Aspinwall
1999-09-29 19:28 ` Lars Magne Ingebrigtsen
1999-09-29 19:33 ` David Aspinwall
1999-09-29 19:52 ` Lars Magne Ingebrigtsen
1999-09-29 19:59 ` Matt Pharr
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=m3so3x37ju.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).