bugmonotone - Bugs: bug #8535, [NEED TEST] monotone log has bad...

 
 

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

bug #8535: [NEED TEST] monotone log has bad defaults outside a working directory

Submitter:  Nathaniel Smith <njs>
Submitted:  Sun 11 Apr 2004 06:37:18 AM UTC
   
 
Category:  command line UI Severity:  3 - Normal
Item Group:  incorrect behavior Status:  Fixed
Privacy:  Public Assigned to:  stephen_leake
Open/Closed:  Closed
mtn version --full: 


Sat 08 May 2010 07:25:37 PM UTC, comment #4: 

For first time users it might still be cool to have -b foo resolving automatically to --from h:foo, no? And this should also reasonable easy to implement...

Thomas Keller <tommyd>
Group administrator
Sat 08 May 2010 07:17:40 PM UTC, comment #3: 

but this works nicely:

      mtn --db ~/monotone-dbs/mtn.db log --from h:net.venge.monotone --last 5
      mtn: expanding selection 'h:net.venge.monotone'
      mtn: expanded to '3085ca18b6493371676bbd39d757ff29112404bc'
      ...

I think we can just close this one

Stephen Leake <stephen_leake>
Group Member
Sat 08 May 2010 07:08:59 PM UTC, comment #2: 

in 0.47, 'mtn log' outside a workspace gives:

   mtn: misuse: workspace required but not found
   mtn: misuse: try passing a --from revision to start at

This is also annoying:
     mtn --db ~/monotone-dbs/mtn.db log --branch net.venge.monotone --last 5
     mtn: option error: unknown option 'branch'

Stephen Leake <stephen_leake>
Group Member
Mon 21 Feb 2005 11:52:04 PM UTC, comment #1: 

This bug needs a (possibly XFAILed) test written.

Nathaniel Smith <njs>
Group Member
Sun 11 Apr 2004 06:37:18 AM UTC, original submission:  

"monotone log" with no further arguments, outside of a working directory, will default to listing the history of the empty manifest.  This is counterintuitive and totally useless.

Rather, if --branch is provided, log should start with the head of that branch.  If there are multiple heads, I'm not sure what the correct behaviour is -- probably it should either
  -- log all heads
  -- log all heads but print a warning that it is doing so
  -- error out, listing the available heads and requesting
     the user pick one.

If --branch is not provided, log should give an error message requesting that the user provide either a branch or a manifest id.

Nathaniel Smith <njs>
Group Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by tommyd (Posted a comment)
  • -email is unavailable- added by stephen_leake (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-05-10 stephen_leake Open/ClosedIn Test Closed
    2010-05-08 stephen_leake StatusNone Fixed
        Open/ClosedOpen In Test
    2010-05-08 stephen_leake Assigned toNone stephen_leake
    2005-02-21 njs Summarymonotone log has bad defaults outside a working directory [NEED TEST] monotone log has bad defaults outside a working directory

    Back to the top

    Powered by Savane 3.13-bb6a.
    Corresponding source code