bugmonotone - Bugs: bug #5247, "monotone co" -vs-...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #5247: "monotone co" -vs- working tree

Submitted by:  Tom Tromey <tromey>
Submitted on:  Fri 12 Sep 2003 09:27:24 PM UTC  
 
Category: command line UISeverity: 1 - Wish
Item Group: incorrect behaviorStatus: Wont Fix
Privacy: PublicAssigned to: graydon hoare <graydon>
Open/Closed: Declined
mtn version --full: 

Wed 01 Oct 2003 09:38:50 PM UTC, comment #1:

'co' command changed to require explicit directory argument; if you provide '.' as the explicit directory, you get what you asked for.

graydon hoare <graydon>
Project MemberIn charge of this item.
Fri 12 Sep 2003 09:27:24 PM UTC, original submission:

Right now if you run "monotone co" in an existing
working tree, it will silently be overwritten.

I think this is a bit unfriendly. Instead we could
either take cvs' approach, where co is like update in
a working tree, or we could simply print an error
and require "monotone co --force" in this situation.

Tom Tromey <tromey>
Project Member

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 6 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Wed 01 Oct 2003 09:38:50 PM UTCgraydonCategoryNone=>(Error - Not Found)
  Severity3 - Normal=>(Error - Not Found)
  Item GroupNone=>(Error - Not Found)
  StatusNone=>(Error - Not Found)
  Assigned toNone=>NA
  Open/ClosedOpen=>(Error - Not Found)

Back to the top


Powered by Savane 3.1-cleanup1