Sponsored Content
Full Discussion: Subversion
Operating Systems Linux Subversion Post 60602 by cbkihong on Wednesday 19th of January 2005 09:33:20 AM
Old 01-19-2005
Subversion is my version control system of choice for managing the LaTeX sources of a book I am working on personally, though I store most of my other scripts or Web site content in CVS server instead.

Working with CVS command line options can be a horrendous experience for new users, as option values sometimes need to be given in certain order, or that the same switch may appears twice in a command but serving different purposes. e.g.:

cvs -d :pserver:anonymous@host:/home/cvsroot co -d tutorial/ tutorial

I am impressed by Subversion for a number of reasons:
- It has less tricky dark corners compared with CVS. CVS has certain behaviour that are not intuitive unless you have read the relevant sections of the manual.
- It supports file copy/rename without losing revision history. A feature I find most useful as I don't make good filenames usually at the very start.
- It does not distinguish binary/ASCII files. Some CVS front ends are prone to always add files in binary mode, making it difficult for some CVS clients to get context diffs even though it simply involves text data.
- Repository-wide revision numbers allow state at any instant to be consistently reproduced. With CVS, you can only be reliably achieving this by tagging often. Checkout by date/time with CVS does not necessarily produce a local copy at any consistent state, depending on the frequency of commits. Per-file revision is more intuitive IMO, though.

Personally I am more used to CVS, but I appreciate SVN's new features.
 

5 More Discussions You Might Find Interesting

1. Solaris

Looking for a subversion GUI for Solaris 9

If available. Didn't see any on the tigris website. Don't have the programming experience to create one. Any third party software would do, too. Client isn't command line friendly. (1 Reply)
Discussion started by: ECBROWN
1 Replies

2. HP-UX

Binaries/Depot for Subversion 1.4.3 for HP/UX 11.11

Could anyone help me out by providing binaries/depot for subversion 1.4.3? The hpux version is: HP-UX myhappybox B.11.11 U 9000/800 I am having trouble compiling the sources for hpux, the provided dependancies are extracted, but it continually falls over. We have previously had svn... (3 Replies)
Discussion started by: spud
3 Replies

3. Linux

KDevelop And Subversion

Hi How I Can Configure KDevelop to Use A Subversion on Local Network System. When I Want to Create New Project, I See A Error With This Message: "Fail to create project directories on repository" What is My Problem??? Help Me Please!!! My KDevelop Version is: 3.0.5 My Subversion is: 1.5.0 ... (0 Replies)
Discussion started by: hotjava
0 Replies

4. UNIX for Advanced & Expert Users

Problem with Subversion SVN

Hi, I am trtying to install SVN server with Apache. I have already configured apache with SVN modulesh and the same can be seen in the modules directory. -rwxr-xr-x 1 root root 34740 Jul 3 13:43 mod_authz_svn.so -rwxr-xr-x 1 root root 385133 Jul 3 13:43 mod_dav_svn.so now the... (1 Reply)
Discussion started by: Siddheshk
1 Replies

5. Web Development

About Apache Subversion

Hi all, I have a trouble with this, the web server include a website and also config as apache subversion, this server crashed and i moved the HDD to another machine, i started all the services and the subversion worked fine, but when i access to the website, this message appear A username and... (0 Replies)
Discussion started by: kidzer0
0 Replies
GIT-CVSEXPORTCOMMIT(1)						    Git Manual						    GIT-CVSEXPORTCOMMIT(1)

NAME
git-cvsexportcommit - Export a single commit to a CVS checkout SYNOPSIS
git cvsexportcommit [-h] [-u] [-v] [-c] [-P] [-p] [-a] [-d cvsroot] [-w cvsworkdir] [-W] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID DESCRIPTION
Exports a commit from GIT to a CVS checkout, making it easier to merge patches from a git repository into a CVS repository. Specify the name of a CVS checkout using the -w switch or execute it from the root of the CVS working copy. In the latter case GIT_DIR must be defined. See examples below. It does its best to do the safe thing, it will check that the files are unchanged and up to date in the CVS checkout, and it will not autocommit by default. Supports file additions, removals, and commits that affect binary files. If the commit is a merge commit, you must tell git cvsexportcommit what parent the changeset should be done against. OPTIONS
-c Commit automatically if the patch applied cleanly. It will not commit if any hunks fail to apply or there were other problems. -p Be pedantic (paranoid) when applying patches. Invokes patch with --fuzz=0 -a Add authorship information. Adds Author line, and Committer (if different from Author) to the message. -d Set an alternative CVSROOT to use. This corresponds to the CVS -d parameter. Usually users will not want to set this, except if using CVS in an asymmetric fashion. -f Force the merge even if the files are not up to date. -P Force the parent commit, even if it is not a direct parent. -m Prepend the commit message with the provided prefix. Useful for patch series and the like. -u Update affected files from CVS repository before attempting export. -k Reverse CVS keyword expansion (e.g. $Revision: 1.2.3.4$ becomes $Revision$) in working CVS checkout before applying patch. -w Specify the location of the CVS checkout to use for the export. This option does not require GIT_DIR to be set before execution if the current directory is within a git repository. The default is the value of cvsexportcommit.cvsdir. -W Tell cvsexportcommit that the current working directory is not only a Git checkout, but also the CVS checkout. Therefore, Git will reset the working directory to the parent commit before proceeding. -v Verbose. CONFIGURATION
cvsexportcommit.cvsdir The default location of the CVS checkout to use for the export. EXAMPLES
Merge one patch into CVS $ export GIT_DIR=~/project/.git $ cd ~/project_cvs_checkout $ git cvsexportcommit -v <commit-sha1> $ cvs commit -F .msg <files> Merge one patch into CVS (-c and -w options). The working directory is within the Git Repo $ git cvsexportcommit -v -c -w ~/project_cvs_checkout <commit-sha1> Merge pending patches into CVS automatically -- only if you really know what you are doing $ export GIT_DIR=~/project/.git $ cd ~/project_cvs_checkout $ git cherry cvshead myhead | sed -n 's/^+ //p' | xargs -l1 git cvsexportcommit -c -p -v GIT
Part of the git(1) suite Git 1.7.10.4 11/24/2012 GIT-CVSEXPORTCOMMIT(1)
All times are GMT -4. The time now is 12:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy