[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: named changesets

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-10-12 03:47:31 CEST

On 10/11/06, Ed S. Peschko <esp5@pge.com> wrote:
> hey all,
> I was wondering - how are named changesets implemented in subversion? We are looking
> at (amongst others) subversion and perforce, and this seems to be a feature that we
> couldn't really live without.. Basically I'd like to say:
> svn commit --name=<changeset_name>

Perforce tracks all changesets on the server. Subversion doesn't do
that; the server doesn't track any sort of client data whatsoever.

However, a subversion client *does* have simple bookkeeping that
allows you to define and name changesets, and commit them exactly as
you show above.

> and at a later point, say something like
> svn merge --name=<changeset_name> --branch=HEAD

Once you commit to subversion, the commit gets a permanent changeset
name in the server, just a large integer. When you want to merge a
changeset from one branch to another, you just use the changeset
number. So yeah, it's pretty darn close to what you're showing.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 12 03:47:45 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.