From: Matt Pharr <mmp@graphics.stanford.edu>
Subject: Re: [COMMIT] Fix for the enable-multibyte-characters problem
Date: 29 Sep 1999 12:59:01 -0700 [thread overview]
Message-ID: <kh0ogelzdyy.fsf@abuffer.stanford.edu> (raw)
In-Reply-To: David Aspinwall's message of "29 Sep 1999 12:16:44 -0700"
> >From the CVS docs:
>
> The diff command is used to compare different revisions of files. The
> default action is to compare your working files *with the revisions
> they were based on*, and report any differences that are found.
Hmm. I swear that I tried doing a cvs update after Didier's checkin and
that I didn't get anything (cvs diff seemed like a better example to send
to the list as a test case), but now an update did give me something, so
all seems well.
Hmm.
-matt
--
Matt Pharr mmp@graphics.stanford.edu
<URL:http://graphics.stanford.edu/~mmp>
prev parent reply other threads:[~1999-09-29 19:59 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
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 [this message]
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=kh0ogelzdyy.fsf@abuffer.stanford.edu \
--to=mmp@graphics.stanford.edu \
/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).