`
nigelzeng
  • 浏览: 605743 次
  • 性别: Icon_minigender_1
  • 来自: 杭州
社区版块
存档分类
最新评论

svn update命令小记

阅读更多

今天在使用svn update命令的时候,出现了这么一个提示:

 

ATTENTION! Your password for authentication realm:
<http://nigel.zeng.me:80> Subversion repository
can only be stored to disk unencrypted! You are advised to configure
your system so that Subversion can store passwords encrypted, if
possible. See the documentation for details.

You can avoid future appearances of this warning by setting the value
of the 'store-plaintext-passwords' option to either 'yes' or 'no' in
'/home/nigelzeng/.subversion/servers'.

 

 

这段文字是svn提示需要做svn 认证的cache,提示你只能把密码不加密(也许是明文)保存,问你是yes or no,

其实输入yes就OK了。

 

单机操作的话没问题,但是在使用脚本批量操作的时候,脚本会卡在这里。(OK,你可以用expect解决,但那是特殊情况)

一般情况下如何跳过这个提示进行操作?

请教了我师兄之后得出了答案:

 

使用这个命令就OK: “ svn update --no-auth-cache”

 

--no-auth-cache:

        Prevents caching of authentication information (e.g. username and password) in the Subversion administrative directories.

 

---------------------------------------------丑陋的分割线--------------------------------------------

 

那svn还有那些附加选项呢?我这里做了一下摘抄:

 

svn Options
While Subversion has different options for its subcommands, all options are global—that is, each option is guaranteed to mean the same thing regardless of the subcommand you use it with. For example, --verbose (-v) always means “verbose output”, regardless of the subcommand you use it with.

--auto-props
Enables auto-props, overriding the enable-auto-props directive in the config file.

--change (-c) ARG
Used as a means to refer to a specific “change” (aka a revision), this option is syntactic sugar for “-r ARG-1:ARG”.

--config-dir DIR
Instructs Subversion to read configuration information from the specified directory instead of the default location (.subversion in the user's home directory).

--diff-cmd CMD
Specifies an external program to use to show differences between files. When svn diff is invoked without this option, it uses Subversion's internal diff engine, which provides unified diffs by default. If you want to use an external diff program, use --diff-cmd. You can pass options to the diff program with the --extensions option (more on that later in this section).

--diff3-cmd CMD
Specifies an external program to use to merge files.

--dry-run
Goes through all the motions of running a command, but makes no actual changes—either on disk or in the repository.

--editor-cmd CMD
Specifies an external program to use to edit a log message or a property value. See the editor-cmd section in the section called “Config”for ways to specify a default editor.

--encoding ENC
Tells Subversion that your commit message is encoded in the charset provided. The default is your operating system's native locale, and you should specify the encoding if your commit message is in any other encoding.

--extensions (-x) ARGS
Specifies an argument or arguments that Subversion should pass to an external diff command. This option is valid only when used with the svn diff or svn merge commands, with the --diff-cmd option. If you wish to pass multiple arguments, you must enclose all of them in quotes (for example, svn diff --diff-cmd /usr/bin/diff -x "-b -E").

--file (-F) FILENAME
Uses the contents of the named file for the specified subcommand, though different subcommands do different things with this content. For example, svn commit uses the content as a commit log, whereas svn propset uses it as a property value.

--force
Forces a particular command or operation to run. There are some operations that Subversion will prevent you from doing in normal usage, but you can pass the force option to tell Subversion “I know what I'm doing as well as the possible repercussions of doing it, so let me at 'em”. This option is the programmatic equivalent of doing your own electrical work with the power on—if you don't know what you're doing, you're likely to get a nasty shock.

--force-log
Forces a suspicious parameter passed to the --message (-m) or --file (-F) options to be accepted as valid. By default, Subversion will produce an error if parameters to these options look like they might instead be targets of the subcommand. For example, if you pass a versioned file's path to the --file (-F) option, Subversion will assume you've made a mistake, that the path was instead intended as the target of the operation, and that you simply failed to provide some other—unversioned—file as the source of your log message. To assert your intent and override these types of errors, pass the --force-log option to subcommands that accept log messages.

--help (-h or -?)
If used with one or more subcommands, shows the built-in help text for each subcommand. If used alone, it displays the general client help text.

--ignore-ancestry
Tells Subversion to ignore ancestry when calculating differences (rely on path contents alone).

--ignore-externals
Tells Subversion to ignore external definitions and the external working copies managed by them.

--incremental
Prints output in a format suitable for concatenation.

--limit NUM
Show only the first NUM log messages.

--message (-m) MESSAGE
Indicates that you will specify a either a log message or a lock comment on the command line, following this option. For example:

$ svn commit -m "They don't make Sunday."
--new ARG
Uses ARG as the newer target (for use with svn diff).

--no-auth-cache
Prevents caching of authentication information (e.g. username and password) in the Subversion administrative directories.

--no-auto-props
Disables auto-props, overriding the enable-auto-props directive in the config file.

--no-diff-added
Prevents Subversion from printing differences for added files. The default behavior when you add a file is for svn diff to print the same differences that you would see if you had added the entire contents of an existing (empty) file.

--no-diff-deleted
Prevents Subversion from printing differences for deleted files. The default behavior when you remove a file is for svn diff to print the same differences that you would see if you had left the file but removed all the content.

--no-ignore
Shows files in the status listing that would normally be omitted since they match a pattern in the global-ignores configuration option or the svn:ignore property. See the section called “Config” and the section called “Ignoring Unversioned Items” for more information.

--no-unlock
Don't automatically unlock files (the default commit behavior is to unlock all files listed as part of the commit). See the section called “Locking” for more information.

--non-interactive
In the case of an authentication failure, or insufficient credentials, prevents prompting for credentials (e.g. username or password). This is useful if you're running Subversion inside of an automated script and it's more appropriate to have Subversion fail than to prompt for more information.

--non-recursive (-N)
Stops a subcommand from recursing into subdirectories. Most subcommands recurse by default, but some subcommands—usually those that have the potential to remove or undo your local modifications—do not.

--notice-ancestry
Pay attention to ancestry when calculating differences.

--old ARG
Uses ARG as the older target (for use with svn diff).

--password PASS
Indicates that you are providing your password for authentication on the command line—otherwise, if it is needed, Subversion will prompt you for it.

--quiet (-q)
Requests that the client print only essential information while performing an operation.

--recursive (-R)
Makes a subcommand recurse into subdirectories. Most subcommands recurse by default.

--relocate FROM TO [PATH...]
Used with the svn switch subcommand, changes the location of the repository that your working copy references. This is useful if the location of your repository changes and you have an existing working copy that you'd like to continue to use. See svn switch for an example.

--revision (-r) REV
Indicates that you're going to supply a revision (or range of revisions) for a particular operation. You can provide revision numbers, revision keywords or dates (in curly braces), as arguments to the revision option. If you wish to provide a range of revisions, you can provide two revisions separated by a colon. For example:

$ svn log -r 1729
$ svn log -r 1729:HEAD
$ svn log -r 1729:1744
$ svn log -r {2001-12-04}:{2002-02-17}
$ svn log -r 1729:{2002-02-17}
See the section called “Revision Keywords” for more information.

--revprop
Operates on a revision property instead of a property specific to a file or directory. This option requires that you also pass a revision with the --revision (-r) option.

--show-updates (-u)
Causes the client to display information about which files in your working copy are out-of-date. This doesn't actually update any of your files—it just shows you which files will be updated if you run svn update.

--stop-on-copy
Causes a Subversion subcommand which is traversing the history of a versioned resource to stop harvesting that historical information when a copy—that is, a location in history where that resource was copied from another location in the repository—is encountered.

--strict
Causes Subversion to use strict semantics, a notion which is rather vague unless talking about specific subcommands (namely, svn propget).

--targets FILENAME
Tells Subversion to get the list of files that you wish to operate on from the filename you provide instead of listing all the files on the command line.

--username NAME
Indicates that you are providing your username for authentication on the command line—otherwise, if it is needed, Subversion will prompt you for it.

--verbose (-v)
Requests that the client print out as much information as it can while running any subcommand. This may result in Subversion printing out additional fields, detailed information about every file, or additional information regarding its actions.

--version
Prints the client version info. This information not only includes the version number of the client, but also a listing of all repository access modules that the client can use to access a Subversion repository. With --quiet (-q) it prints only the version number in a compact form.

--xml
Prints output in XML format.

 

 

that's all.

分享到:
评论

相关推荐

    svn在linux下的使用(svn命令)

    svn update 命令用于更新到某个版本。例如:svn update -r 200 test.php(将版本库中的文件 test.php 还原到版本 200) 6. 查看文件或者目录状态 svn status 命令用于查看文件或者目录的状态。例如:svn status ...

    SVN常用命令集合及简单用法

    SVN常用命令集合及简单用法 SVN(Subversion)是一种版本控制系统,用于管理代码、文档、图片等文件的版本变更。下面是常用的 SVN 命令集合及简单用法: 1. 检出文件:svn checkout path(path 是服务器上的目录)...

    svn 删除文件 update 又出来了 怎么回事

    在使用版本控制系统Subversion(简称svn)时,可能会遇到一些操作上的困扰,比如在尝试删除文件后,通过`svn update`命令更新代码时,已经删除的文件却又重新出现了。这通常是由svn的工作方式引起的,我们需要理解其...

    svn命令大全.docx

    "svn命令大全" SVN(Subversion)是一种版本控制系统,主要用于管理软件开发过程中的代码修改和更新。下面是 Linux 下 SVN 命令大全介绍: 一、checkout 命令 checkout 命令用于将文件从服务器 checkout 到本地...

    linux下SVN常用命令

    ### Linux下SVN常用命令详解 #### 一、SVN Checkout **命令格式:** ```shell svn checkout [URL] [本地路径] ``` **功能介绍:** 此命令用于将远程版本库中的某个目录或文件检出到本地,创建一个工作副本。 **示例...

    svn服务用svnsync命令双机热备

    ### SVN服务用svnsync命令实现双机热备 #### 概述 在软件开发过程中,版本控制系统(Version Control System, VCS)是必不可少的工具之一。Subversion(SVN)作为一款广受欢迎的集中式版本控制系统,在企业级项目...

    svn常用命令介绍

    4. **更新(svn update)**: 更新本地工作副本与仓库中的最新版本同步,使用`svn up`命令。 5. **提交(svn commit)**: 将本地工作副本的更改推送到仓库,`svn ci -m "提交消息"`,`-m`后是提交的描述。 6. *...

    SVN在客户端执行UPDATE报locked的处理办法

    在日常使用SVN的过程中,开发者可能会遇到各种各样的问题,比如在执行`svn update`命令时出现“locked”的错误提示。本文将详细介绍这一问题的原因、常见场景以及如何有效解决。 #### 错误现象 当在SVN客户端执行`...

    svn linux下命令详解

    svn update 命令用于将文件更新到某个版本。该命令的基本语法为:svn update -r &lt;版本号&gt; &lt;文件名&gt;。例如:svn update -r 200 test.php(将版本库中的文件 test.php 还原到版本 200)。 6. 查看文件或者目录状态 ...

    svn常见问题及解决

    你可以选择删除本地文件并执行`update`来获取最新版本。 5. **灰色向右箭头(本地修改)**: 说明你修改了文件但未提交。确保适时提交你的更改。 6. **蓝色向左箭头(SVN上修改)**: 提醒你更新代码后再进行修改,确保...

    SVN自动更新脚本(可改时间间隔)

    ②【ws.run "D:\SVN自动更新脚本\svnUpdate.bat",0】,地址更改为svnUpdate.bat存放地址即可 svnUpdate.bat 中【::】后为注释 主要进行以下修改 ①D:\svn为待更新的SVN目录,就是执行update的目录,改成你需要执行...

    svn 回退/更新/取消至某个版本命令

    `svn update`(或简写为`svn up`)是SVN中最常用的命令之一,用于将版本库中的更改合并到工作副本中。 - **基本用法**:`svn update [PATH]` - 如果没有指定版本号,则默认更新到`HEAD`版本。 - 否则,会同步到由...

    获取svn最新版本号示例 以及svn常用命令

    2. **`svn update` (简写:`svn up`)**:更新本地工作副本到最新版本,格式为`svn update [PATH]`。 3. **`svn commit` (简写:`svn ci`)**:提交本地更改到仓库,格式为`svn commit -m "提交信息" [PATH]`。 4. **`...

    windows系统下svn update失败的解决方法,绝对有效

    解决windows系统下,update失败,并且cleanup后再update也失败的问题,虽然谷歌百度也能解决但是你需要花费很多时间去找到自己需要的,我这里是详细总结后的实践步骤,亲测一直可行,谢谢支持。

    svn启动命令

    svn启动命令

    linux下svn命令大全.txt

    `svn update [-r revision] path` 命令用于将工作副本更新到最新版本,或者指定版本号进行更新。例如,`svn update -r 200 test.php` 将文件“test.php”更新至版本200。 ### 6. 查看状态 (Status) `svn status ...

    linux下svn命令大全.pdf

    使用 `svn update` 命令可以将文件更新到最新版本。例如,更新当前目录下的所有文件可以使用: `svn update` 查看文件状态 使用 `svn status` 命令可以查看文件或目录的状态。例如,查看当前目录下的文件状态可以...

    SVN基础命令

    svn基础命令,主要整理了SVN使用终端控制的create、up、commit等

Global site tag (gtag.js) - Google Analytics