bugmonotone - Bugs: bug #30291, Less verbose restriction warnings

 
 

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

bug #30291: Less verbose restriction warnings

Submitter:  Thomas Keller <tommyd>
Submitted:  Tue 29 Jun 2010 11:22:42 AM UTC
   
 
Category:  command line UI Severity:  3 - Normal
Item Group:  code cleanup Status:  Fixed
Privacy:  Public Assigned to:  None
Open/Closed:  Closed
mtn version --full: 

mtn-0.48

Fri 09 Jul 2010 08:22:24 AM UTC, comment #1: 

Fixed in 8b113b28b884620487db0a0759d0a52aafdb12fd and merged

Thomas Keller <tommyd>
Group administrator
Tue 29 Jun 2010 11:22:42 AM UTC, original submission:  

It would be cool if we could make the warnings about the inclusion of parents in a restriction less verbose.

Right now if a specific file is targeted in a/b/c/, we emit four warnings, which is imho a little bit too much:

mtn: warning: including missing parent ''
mtn: warning: including missing parent 'a'
mtn: warning: including missing parent 'a/b'
mtn: warning: including missing parent 'a/b/c'

So if I got it right, the warnings are there to inform the user that other changes (renames, attribute changes) in any of the parent directories are committed along with the targeted file. But if no such changes exist, the warnings are pointless...

I think what we actually want and need is a way to give the roster some meta information about "explicit" and "implicit" changes and output these at a place when we compare the old against the new roster, i.e. before creating the new revision. Would that be a feasible approach?


Thomas Keller <tommyd>
Group administrator

 

(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 (Submitted the item)
  •  

    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 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-07-09 tommyd StatusNone Fixed
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code