Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

SVN : What's the difference between --non-interactive and --accept postpone ?

Tags:

svn

I'm trying to understand the difference between those two option of the svn update command. I have, admittedly quickly, looked at the book but didn't find anything useful.

I also tried both with conflicts, and both display the same text, and so on (svn version 1.6.12). Nothing about that on the web.

Thanks a lot !

like image 614
4wk_ Avatar asked Mar 06 '13 13:03

4wk_


People also ask

What is svn commit and update?

Read the SVN book, or at least the chapter about fundamental concepts and basic usage. Update means: "take all the new stuff in the repository and apply them in my working copy". Commit means: "take all the changes I've made in my working copy and apply them in the repository"

What is in svn status?

svn status (stat, st) — Print the status of working copy files and directories.

How can I tell if svn client is installed on Linux?

SVN Installation To check whether it is installed or not use following command. If Subversion client is not installed, then command will report error, otherwise it will display the version of the installed software. If you are using RPM-based GNU/Linux, then use yum command for installation.


1 Answers

When you have a question about Apache Subversion refer to SVNBook.

  • --non-interactive is a global option and means "do no interactive prompting",

  • --accept postpone is a valid option of svn update command and means "take no resolution action at all and instead allow the conflicts to be recorded for future resolution".

Global options apply to all svn.exe subcommands, even if they have no effect on some of them, see http://svnbook.red-bean.com/en/1.7/svn.ref.svn.html#svn.ref.svn.sw:

The svn command-line client usually exits quickly with an error if you pass it an option which does not apply to the specified subcommand. But as of Subversion 1.5, several of the options which apply to all—or nearly all—of the subcommands have been deemed acceptable by all subcommands, even if they have no effect on some of them. (This change was made primarily to improve the client's ability to called from custom wrapping scripts.) These options appear grouped together in the command-line client's usage messages as global options, as can be seen in the following bit of output.

like image 142
bahrep Avatar answered Oct 27 '22 15:10

bahrep