The first part of the visual git tutorial explains how to locally track project files with the git version control system. It shows how to add and commit changes, how to browse the history, revert changes and how to work with tags and branches.
iston eases your vendor branch management worries. A vendor branch is when you copy a vendor's code (plugins, gems, etc) inside your own repository / project.
What are the advantages of doing that?
* You don't depend on another repository to deploy to your staging or production machines;
* You are insulated from upstream changes, until you really want those changes and have a chance to test them;
* Piston allows you to apply local patches to your vendor code, until the upstream maintainers have applied them.
This web-based tool is based on plain JSF. It aims to provide support for all features of JCR-Repository including optional features like versioning.
The specification for JCR 1.0 can be found here , the work in progress for 2.0 can be found here: here .
For development the implementation Apache Jackrabbit is used, which can be found here: here .
rsvndump is a command line tool that is able to dump a Subversion repository that resides on a remote server. All data is dumped in the format that can be read an written by svnadmin dump, so the data which is produced can easily be importerd into a new Subversion repository.
Actually, a remote dump can be done using svnsync and svnadmin dump on the locally synced repository. However, if the remote server does not run Subversion 1.5 or later, svnsync is unable to dump subdirectories of a repository only. This can be solved by syncing the whole repository and using svndumpfilter afterwards, but data of other subdirectories needs to be transferred over the network for no reason. And if you don't have access to the repository root, the whole thing will not work.
Long story short: If you want to dump a subdirectory of a remote repository which runs a version of Subversion prior to 1.5, this is the right tool for you. If not, please consider using svnsync.
rsvndump is written in C and built on top of the Subversion API, so it can offer all functionality needed to access a Subversion repository, including SSL authentication. And it's GPLed.
The Envers project aims to enable easy versioning of persistent JPA classes. All that you have to do is annotate your persistent class or some of its properties, that you want to version, with @Versioned. For each versioned entity, a table will be created, which will hold the history of changes made to the entity. You can then retrieve and query historical data without much effort.
Similarly to Subversion, the library has a concept of revisions. Basically, one transaction commit is one revision (unless the transaction didn't modify any versioned entities). As the revisions are global, having a revision number, you can query for various entities at that revision, retrieving a (partial) view of the database at that revision.
monotone is a free distributed version control system. it provides a simple, single-file transactional version store, with fully disconnected operation and an efficient peer-to-peer synchronization protocol. it understands history-sensitive merging, lightweight branches, integrated code review and 3rd party testing.
Subversion’s hook scripts provide a powerful and flexible way to associate actions with repository events. For example, the pre-commit hook allows you to check — and possibly abort — a transaction before it actually gets committed. This entry describes how to install and test a simple Python hook script to prohibit tabs from C++ files.
While Subversion will do a fine job of storing all of the files you want revisioned, it can do quite a bit more. For example, it could send an eMail to a list of users every time a commit is made, to help ensure that at least one more set of eyeballs looks at critical bits of code before they get deployed into production environments. It can allow some users (but not others) to alter some properties (but not others). It can automatically attempt a recompile of code on a particular branch whenever commits are made, inform users as to the outcome of that compile, and even push those changes to a test machine for live experimentation. Subversion's triggers, or hook scripts, can be as simple or as complex as you desire.
WebSVN offers a view onto your subversion repositories that's been designed to reflect the Subversion methodology. You can view the log of any file or directory and see a list of all the files changed, added or deleted in any given revision. You can also view the differences between 2 versions of a file so as to see exactly what was changed in a particular revision.
SVNBrowser is a Java webapp which provides friendly web access to a Subversion repository. It goes above and beyond the browser interface provided by mod_svn and mod_dav_svn by providing the ability to upload files to a Subversion repository (users may either add a new file or replace an existing file with a new version), to replace existing files with a new copy (automatically generating diffs against the old), to delete files, to create and delete directories, and to move files. It also features an access control system by which only certain parts of a repository are made visible to end users (for example, if you want web users to be restricted to seeing and modifying content inside the "/docs" directory within your project).
Shotoku is designed to provide easy access to content repositories in which you can store data, bind metadata, revision content, and provide branching and merging strategies. This means Shotoku can interface with repositories such as the Java Content Repo
KDESvn is a frontend to the subversion vcs. In difference to most other tools it uses the subversion C-Api direct via a c++ wrapper made by Rapid SVN and doesn't parse the output of the subversion client. So it is a real client itself instead of a fronten