A BUGNOTE has been added to this bug.
======================================================================
http://dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000090
======================================================================
Reported By:                paul
Assigned To:                
======================================================================
Project:                    DBMail
Bug ID:                     90
Category:                   Command-Line programs (dbmail-users, dbmail-util)
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     confirmed
======================================================================
Date Submitted:             15-Sep-04 12:45 CEST
Last Modified:              15-Sep-04 17:04 CEST
======================================================================
Summary:                    -n switch is non-functional for dbmail-util
Description: 
Despite using -n actions are still performed.
======================================================================

----------------------------------------------------------------------
 ilja - 15-Sep-04 15:37 CEST 
----------------------------------------------------------------------
The same seems to be the fact for dbmail-users.

Aaron, is this intented, is it a slip?

Should we perhaps just remove the documentation for the '-n' option? (from
man-pages and on-line help)

----------------------------------------------------------------------
 aaron - 15-Sep-04 17:04 CEST 
----------------------------------------------------------------------
Gaa, there I go again. I remember looking at the queries involved in
database cleanup and not figuring out how I was going to implement proper
output for, say, 'dbmail-util -nv -cturpd' where it should tell you all
about what it wants to fix but not actually fix anything... and then
moving onto other parts of the project and not getting back to those
queries :-\

I suppose we should pull -n for now, unless there's some trivially simple
logic to prevent actions from being taken that I didn't see the first time
around. I would suggest using the same type of error message as is
currently being used for '-i' interactive option (which may never be
implemented, but I thought it would be appropriate to reserve the option
letter in all of the binaries).

Bug History
Date Modified  Username       Field                    Change              
======================================================================
15-Sep-04 12:45paul           New Bug                                      
15-Sep-04 15:37ilja           Bugnote Added: 0000247                       
15-Sep-04 15:39ilja           Status                   new => confirmed    
15-Sep-04 17:04aaron          Bugnote Added: 0000250                       
======================================================================

Reply via email to