조회 수 18795 추천 수 0 댓글 0
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄
Extra Form

제외

svn update --set-depth exclude directoryName

원복

svn update --set-depth infinity

TAG •

Version
2011.09.01 10:40

Sub Version / 저장소 URL 변경

조회 수 27604 추천 수 0 댓글 0
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄
Extra Form

# svn switch --relocate file:///old/repos file:///new/location .

TAG •

Version
2009.12.24 10:28

Sub Version에 vimdiff 설정하기

조회 수 23035 추천 수 0 댓글 0
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄
Extra Form

1. PATH에 등록된 디렉토리에 vimdiff.sh 파일을 생성한다.

~/.bash_profile에 PATH=$PATH;$HOME/bin 을 추가해 주면 됨.

2. vimdiff.sh 내용
#!/bin/bash
while test $# -gt 2; do shift; done
vimdiff $@
3. ~/.subversion/config 파일 수정하기

아래와 같이 diff-cmd를 지정해준다.

diff-cmd = vimdiff.sh 
4. svn diff 파일명 
5. vim 에디터가 열리면서 이전 revision의 것과 변경사항을 확인할 수 있다.


TAG •

Version
2007.12.22 10:04

저장소 만들기

조회 수 25467 추천 수 0 댓글 2
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄
Extra Form
Subversion repository creation is an incredibly simple task. The svnadmin utility that comes
with Subversion provides a subcommand (create) for doing just that.

$ svnadmin create /path/to/repos

This creates a new repository in the directory /path/to/repos, and with the default filesystem
data store. Prior to Subversion 1.2, the default was to use Berkeley DB; the default is now
FSFS. You can explicitly choose the filesystem type using the --fs-type argument, which
accepts as a parameter either fsfs or bdb.

$ # Create an FSFS-backed repository
$ svnadmin create --fs-type fsfs /path/to/repos
$
# Create a Berkeley-DB-backed repository
$ svnadmin create --fs-type bdb /path/to/repos
$

After running this simple command, you have a Subversion repository.
The path argument to svnadmin is just a regular filesystem path and not a URL
like the svn client program uses when referring to repositories. Both svnadmin
and svnlook are considered server-side utilities?they are used on the machine
where the repository resides to examine or modify aspects of the repository, and
are in fact unable to perform tasks across a network. A common mistake made by
Subversion newcomers is trying to pass URLs (even “local” file:// ones) to
these two programs.

Present in the db/ subdirectory of your repository is the implementation of the versioned
filesystem. Your new repository's versioned filesystem begins life at revision 0, which is
defined to consist of nothing but the top-level root (/) directory. Initially, revision 0 also has a
single revision property, svn:date, set to the time at which the repository was created.

Now that you have a repository, it's time to customize it.
While some parts of a Subversion repository?such as the configuration files and
hook scripts?are meant to be examined and modified manually, you shouldn't
(and shouldn't need to) tamper with the other parts of the repository “by hand”. The
svnadmin tool should be sufficient for any changes necessary to your repository,
or you can look to third-party tools (such as Berkeley DB's tool suite) for tweaking
relevant subsections of the repository. Do not attempt manual manipulation of your
version control history by poking and prodding around in your repository's data
store files!

TAG •
  • ?
    GG 2008.01.08 16:01
    버클리DB 너무 자주 깨짐. -_-;
    SVN은 단점을 하나 꼽으라면, 저장공간이 코드사이즈*2 가 필요하다는 것 ㅠ_ㅠ
  • ?
    비트겐스 2008.01.10 10:48
    글쿤emoticon

Version
2007.08.24 09:50

svn / quick start

조회 수 36673 추천 수 0 댓글 0
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄
Extra Form

A Quick Start

Some people have trouble absorbing a new technology by reading the sort of “top down” approach provided by this book. This section is a very short introduction to Subversion, and is designed to give “bottom up” learners a fighting chance. If you prefer to learn by experimentation, the following demonstration will get you up and running. Along the way, we give links to the relevant chapters of this book.

If you're new to the entire concept of version control or to the “copy-modify-merge” model used by both CVS and Subversion, then you should read Chapter 2, Basic Concepts before going any further.

Note

The following example assumes that you have svn, the Subversion command-line client, and svnadmin, the administrative tool, ready to go. It also assumes you are using Subversion 1.2 or later (run svn --version to check.)

Subversion stores all versioned data in a central repository. To begin, create a new repository:

$ svnadmin create /path/to/repos
$ ls /path/to/repos
conf/  dav/  db/  format  hooks/  locks/  README.txt

This command creates a new directory /path/to/repos which contains a Subversion repository. This new directory contains (among other things) a collection of database files. You won't see your versioned files if you peek inside. For more information about repository creation and maintenance, see Chapter 5, Repository Administration.

Subversion has no concept of a “project”. The repository is just a virtual versioned filesystem, a large tree that can hold anything you wish. Some administrators prefer to store only one project in a repository, and others prefer to store multiple projects in a repository by placing them into separate directories. The merits of each approach are discussed in the section called “Choosing a Repository Layout”. Either way, the repository only manages files and directories, so it's up to humans to interpret particular directories as “projects”. So while you might see references to projects throughout this book, keep in mind that we're only ever talking about some directory (or collection of directories) in the repository.

In this example, we assume that you already have some sort of project (a collection of files and directories) that you wish to import into your newly created Subversion repository. Begin by organizing them into a single directory called myproject (or whatever you wish). For reasons that will be clear later (see Chapter 4, Branching and Merging), your project's tree structure should contain three top-level directories named branches, tags, and trunk. The trunk directory should contain all of your data, while branches and tags directories are empty:

/tmp/myproject/branches/
/tmp/myproject/tags/
/tmp/myproject/trunk/
                     foo.c
                     bar.c
                     Makefile
                     …

The branches, tags, and trunk subdirectories aren't actually required by Subversion. They're merely a popular convention that you'll most likely want to use later on.

Once you have your tree of data ready to go, import it into the repository with the svn import command (see the section called “svn import):

$ svn import /tmp/myproject file:///path/to/repos/myproject -m "initial import"
Adding         /tmp/myproject/branches
Adding         /tmp/myproject/tags
Adding         /tmp/myproject/trunk
Adding         /tmp/myproject/trunk/foo.c
Adding         /tmp/myproject/trunk/bar.c
Adding         /tmp/myproject/trunk/Makefile
…
Committed revision 1.
$ 

Now the repository contains this tree of data. As mentioned earlier, you won't see your files by directly peeking into the repository; they're all stored within a database. But the repository's imaginary filesystem now contains a top-level directory named myproject, which in turn contains your data.

Note that the original /tmp/myproject directory is unchanged; Subversion is unaware of it. (In fact, you can even delete that directory if you wish.) In order to start manipulating repository data, you need to create a new “working copy” of the data, a sort of private workspace. Ask Subversion to “check out” a working copy of the myproject/trunk directory in the repository:

$ svn checkout file:///path/to/repos/myproject/trunk myproject
A  myproject/foo.c
A  myproject/bar.c
A  myproject/Makefile
…
Checked out revision 1.

Now you have a personal copy of part of the repository in a new directory named myproject. You can edit the files in your working copy and then commit those changes back into the repository.

  • Enter your working copy and edit a file's contents.

  • Run svn diff to see unified diff output of your changes.

  • Run svn commit to commit the new version of your file to the repository.

  • Run svn update to bring your working copy “up-to-date” with the repository.

    출처: http://svnbook.red-bean.com/en/1.2/svn.intro.quickstart.html

TAG •

Board Pagination Prev 1 Next
/ 1