From: martin rudalics <rudalics@gmx.at>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: vc-cvs-parse-entry
Date: Wed, 30 Aug 2006 19:51:09 +0200 [thread overview]
Message-ID: <44F5D00D.5080409@gmx.at> (raw)
In-Reply-To: <uhczubee3.fsf@gnu.org>
>>So there really is a 1-hour difference between what the CVS/Entries file
>>says and what the file's time stamp says. We could try to be more clever
>>with such situations, but since it's basically a case of braindamage in the
>>w32 "spec" I'd rather not bother.
>
>
> I'm not familiar with the details, nor with vc-cvs in general, so
> what's below might be nonsense; sorry if so.
>
> Is the problem you describe above in Emacs or in the CVS client that
> Emacs runs? If the latter, I agree that some (or maybe all) Windows
> ports of the CVS client don't DTRT in this case.
Eli, please look at what your system tells you about the following two
Emacs files: "src/acldef.h" and "src/alloca.c". I get:
Entries: /acldef.h/1.2/Mon Sep 1 15:45:52 2003//
Emacs: Mon Sep 1 17:45:52 2003
Windows: Mon Sep 1 17:45:52 2003
Entries: /alloca.c/1.29/Fri Jan 30 17:10:02 2004//
Emacs: Fri Jan 30 17:10:02 2004
Windows: Fri Jan 30 18:10:02 2004
Where Entries is the entry from CVS/Entries, Emacs is a prettified
version obtained from `file-attributes', and Windows is what WindowsME
tells me. I fail to understand why the values for `alloca.c' differ for
Windows and Emacs. If these values are identic for you (XP I presume)
than the problem is with Emacs for Windows98/FAT32.
next prev parent reply other threads:[~2006-08-30 17:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 16:20 vc-cvs-parse-entry martin rudalics
2006-08-29 19:07 ` vc-cvs-parse-entry Stefan Monnier
2006-08-29 20:51 ` vc-cvs-parse-entry martin rudalics
2006-08-29 21:06 ` vc-cvs-parse-entry Stefan Monnier
2006-08-30 12:24 ` vc-cvs-parse-entry Eli Zaretskii
2006-08-30 17:51 ` martin rudalics [this message]
2006-09-02 13:10 ` vc-cvs-parse-entry Eli Zaretskii
2006-09-02 13:45 ` vc-cvs-parse-entry martin rudalics
2006-09-02 14:48 ` vc-cvs-parse-entry Eli Zaretskii
2006-09-03 10:40 ` vc-cvs-parse-entry martin rudalics
2006-09-03 21:00 ` vc-cvs-parse-entry Eli Zaretskii
2006-09-04 3:17 ` vc-cvs-parse-entry Eli Zaretskii
2006-09-04 9:17 ` vc-cvs-parse-entry martin rudalics
2006-09-04 17:55 ` vc-cvs-parse-entry Eli Zaretskii
2006-09-05 9:10 ` vc-cvs-parse-entry martin rudalics
2006-09-05 18:31 ` vc-cvs-parse-entry Eli Zaretskii
2006-09-10 9:55 ` vc-cvs-parse-entry martin rudalics
2006-09-10 21:17 ` vc-cvs-parse-entry Eli Zaretskii
2006-09-11 9:41 ` vc-cvs-parse-entry martin rudalics
2006-09-11 14:14 ` vc-cvs-parse-entry Stefan Monnier
2006-09-12 3:50 ` vc-cvs-parse-entry Eli Zaretskii
2006-09-14 8:40 ` vc-cvs-parse-entry martin rudalics
2006-09-15 17:43 ` vc-cvs-parse-entry Eli Zaretskii
2006-09-15 17:51 ` vc-cvs-parse-entry Eli Zaretskii
2006-08-30 21:01 ` vc-cvs-parse-entry Stefan Monnier
2006-09-02 12:32 ` vc-cvs-parse-entry Eli Zaretskii
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=44F5D00D.5080409@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.