[
https://issues.apache.org/jira/browse/SVN-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Foad updated SVN-795:
----------------------------
Component/s: (was: src)
> Need "dry run" option to some commands
> --------------------------------------
>
> Key: SVN-795
> URL: https://issues.apache.org/jira/browse/SVN-795
> Project: Subversion
> Issue Type: New Feature
> Affects Versions: all
> Reporter: Subversion Importer
> Priority: Major
> Fix For: unscheduled
>
>
> {noformat:nopanel=true}
> > > if a short opt is needed.) But would like to know what commands a
> > > "dry-run" mode is useful for -- the classic CVS use case is "cvs -n
> > > update", and we've already got that covered with "svn st -u".
> >
> > cleanup
> > merge
> > resolve (maybe? haven't used this command yet)
> > revert
> > switch
> >
> > As for update, i agree with what someone else suggested on the
> > list, that update -n behave like cvs's did. Sure status -u already
> > has that covered, but maybe you can just reuse that code. If a
> > person wants to see what svn update does, it's logical to think of
> > update -n, not status -u. Sure, status -u will be documented, but
> > if it doesn't interfere with anything else, it seems like a good
> > idea to match expectations.
> This all sounds reasonable. I'm not sure I totally buy the "update
> -n" expectedness argument :-), but no matter, the other examples are
> good ones by themselves.
> Could you file a new Post-1.0 issue about "dry run" support, giving
> the above examples, and noting that patches to implement it before 1.0
> are fine? I don't think we should put such a potential bug source
> into Alpha, but at least this way we won't forget about it.
> {noformat}
> Original issue reported by *epg*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
