[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Trouble with texinfo-multiple-files-update

From: Eli Zaretskii
Subject: Re: Trouble with texinfo-multiple-files-update
Date: Sun, 02 Jun 2013 22:21:12 +0300

> Date: Sun, 2 Jun 2013 19:16:07 +0000
> Cc: address@hidden
> From: Alan Mackenzie <address@hidden>
> > That's what that command does: its default is to update the top-level
> > menu in each individual file that is part of the manual.  Each file is
> > a full chapter.  The updating of the master menu is the optional
> > behavior, invoked with C-u.
> Yes.  My point is, why can't the updating of the master menu, which is a
> coherent action in its own right, be performed independently of updating
> the individual *.texi's?

History, I suppose.

> > Why do you care about files' timestamps?
> I just do.  I find the question rather strange.  Who wouldn't care about
> timestamps?  They provide a rapid, convenient insight into the activity
> in the directory, in fact in any directory.  For example, I see most
> files.texi unchanged since 2013-01-25 (when I presumably cloned the
> repository), and several at various points since (when I updated the
> repo).  killing.texi hasn't been changed at all, but windows.texi was
> changed as recently as May.

That just means you use bzr very little.  The moment you revert some
file, its time stamp changes to the moment of the revert.  So any
significant VCS activity messes up the time stamps.  IOW, the time
stamps are insignificant.  You should become used to not worrying
about them.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]