[Top][All Lists]

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

[Monotone-devel] Updated Issue 135 - need automate get_corresponding_pat

From: code
Subject: [Monotone-devel] Updated Issue 135 - need automate get_corresponding_path for workspace rename (monotone)
Date: Sat, 5 Feb 2011 00:07:31 GMT


The following issue has been updated:

135 - need automate get_corresponding_path for workspace rename
Project: monotone
Status: New
Reported by: Stephen Leake
 Type:Feature Request

Comments (last first):

# By Thomas Keller, Feb  5, 2011:

Its not a bug, ... :)

 Labels: Type:Feature Request, -Type:Incorrect Behavior

# By Stephen Leake, Jan 20, 2011:

Steps to reproduce the problem:

1. in a workspace, use 'mtn mv' to rename a file, but don't commit
2. mtn automate get_corresponding_path <??workspace> <new file name> <base rev>

Expected result:
want the new name of the file in the workspace, but there is no way to get that 
from automate.

Output of `mtn version --full`: 1.0dev

Actually, there is a way; do 'mtn automate inventory', and look for the file. 
But that's cumbersome.

The current syntax of the command is:

mtn automate get_corresponding_path rev1 file rev2

'file' is the filename in rev1; the result is the filename in rev2.

In general, we need to allow either rev1 or rev2 to be the workspace (Emacs DVC 
needs both).

We could introduce two new commands:

'mtn automate get_base_rev_path <file>'

    <file> is current workspace name; return name in workspace base revision.

'mtn automate get_workspace_path <file>'

    <file> is file name in workspace base rev; return name in workspace.


reply via email to

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