monotone-devel
[Top][All Lists]
Advanced

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

[Monotone-devel] [PATCH] mtn publish


From: Ben Walton
Subject: [Monotone-devel] [PATCH] mtn publish
Date: Thu, 21 Dec 2006 10:25:35 -0500

Hi All,

I've attached a patch that adds a toplevel publish command to montone.
I realize that exporting from the db certainly isn't the main focus
of a vcs package, but it is a feature that I will find useful.  For
example, I run a cluster of linux machines with cfengine as my policy
agent.  I'd like to have my cfengine master server periodically
publish the most current files to be picked up by the clients, but I
don't want the clients seeing _MTN/*.  I have various other similar
uses (my dns zone files, etc).

I realize that this could be done with a script also, so if you feel
that this is a silly feature, my feelings will not be hurt if the
patch isn't accepted.

The semantics are almost identical to checkout, except that it will
not checkout to the cwd.  It also introduces a --force option to be
used in the event where the publishing destination directory already
exists.  If the destination exists and is a file, mtn will abort...I
felt that this was more dangerous than overriding a directory.  An
existing directory is backed up and left in place.

2006-12-21  Ben Walton       <address@hidden>
 * cmd_ws_commit.cc (CMD_NO_WORKSPACE(publish)): added this
              command, which exports a revision/branch from the db.
 * options_list.hh: added a --force to be used with publish.
 * monotone.texi: added documentation for the new command.

Thanks
-Ben
--
---------------------------------------------------------------------------------------------------------------------------
Ben Walton <address@hidden>

Unanswered questions are far less dangerous than unquestioned answers.
- The Roadside Pulpit
---------------------------------------------------------------------------------------------------------------------------

Attachment: mtn_publish.diff
Description: Binary data


reply via email to

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