On Thu, 2005-02-24 at 17:39 -0500, Robert Anderson wrote: > The problem is invariably that a config file has been changed, > and the devguy is unaware of this and is confused and frustrated > that he can't get up-to-date by issuing "update" commands. > Frankly, I think he's right to be. You shouldn't always have to > check out from scratch, or sift through commits wondering if > someone changed a config file, manually tweaking your trees if > there was, or write your own hacky scripts that verify the > consistency of configs and tree layouts. It ought to be a > one-off operation to verify that a config is fully checked in on > the one side, and a one-off operation to bring the config up to > date on the other, or verify that it is. > > Maybe this is something the baz guys can think about.
Something like the attached script, for example?
I have wrote it to help me manage production checkouts, where the most
common operation by far is updating a whole config to the latest.
This script _is_ hackish, but that could be a good starting point for
feedback.
--
-- ddaa
config-update
Description: application/python
_______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
