[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-commits-nodiffs] Revision 2834e9d70305b45fe189e160414aa4a85fac
From: |
monotone |
Subject: |
[Monotone-commits-nodiffs] Revision 2834e9d70305b45fe189e160414aa4a85face297 |
Date: |
Sat, 17 Jun 2006 09:08:06 +0200 |
-----------------------------------------------------------------
Revision: 2834e9d70305b45fe189e160414aa4a85face297
Ancestor: 819291783d93dee594afd2885232bfeb466ffcc4
Author: Timothy Brownawell <address@hidden>
Date: 2006-06-17T06:25:35
Branch: net.venge.monotone
Deleted entries:
automate.hh
Modified files:
ChangeLog Makefile.am automate.cc cmd.hh cmd_automate.cc
cmd_list.cc
ChangeLog:
2006-06-17 Timothy Brownawell <address@hidden>
(see bug #15995, asking for a more comprehensive automate command set)
Start splitting up automate.cc . There is now an AUTOMATE() macro in
cmd.hh , similar to the CMD() macro. Individual automate commands can
share a file with similar command-line commands, and many commands can
be factored into an implementation with CMD() and AUTOMATE() wrappers
to format input/output.
* cmd.hh: Add stuff needed to define a new automate command.
* cmd_automate.cc: This gets automate infrastructure similar to
what commands.cc is for command-line commands. And automate stdio.
* cmd_list.cc: "keys" and "certs" automate commands go here
* automate.hh: No longer needed.
* automate.cc: use AUTOMATE() macro for the automate commands that
haven't got a new home yet.
monotone --db={your.database} diff
--revision=819291783d93dee594afd2885232bfeb466ffcc4
--revision=2834e9d70305b45fe189e160414aa4a85face297
----------------------------------------------------------------------
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Monotone-commits-nodiffs] Revision 2834e9d70305b45fe189e160414aa4a85face297,
monotone <=