Something odd just happened

Something odd just happened

[Eric S. Raymond]

Something odd just happened.  During commit. Bazaar listed as
"modified" a file I had not touched: lisp/emacs-lisp/eieio.el

Whoever owns that should check to make sure it's in the right state.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

A ``decay in the social contract'' is detectable; there is a growing
feeling, particularly among middle-income taxpayers, that they are not
getting back, from society and government, their money's worth for
taxes paid. The tendency is for taxpayers to try to take more control
of their finances...	-- IRS Strategic Plan, (May 1984)

Re: Something odd just happened

[David Engster]

Eric S. Raymond writes:
> Something odd just happened.  During commit. 

So you are working with a bound branch?

> Bazaar listed as "modified" a file I had not touched:
> lisp/emacs-lisp/eieio.el

It contains generated autoloads, so it can change during build if the
other eieio* files were changed (rev. 115955).

> Whoever owns that should check to make sure it's in the right state.

It is.

-David

Re: Something odd just happened

[Eli Zaretskii]

> From: esr@thyrsus.com (Eric S. Raymond)
> Date: Fri, 10 Jan 2014 12:17:55 -0500 (EST)
> 
> Something odd just happened.  During commit. Bazaar listed as
> "modified" a file I had not touched: lisp/emacs-lisp/eieio.el

Some of the *.el files have autoload cookies in them, which can be
updated when other Lisp files are updated.  It's normal.

When this happens, you can either commit the modified file (as a
separate commit, please), or revert it and wait for someone else to do
that.