* Ben Collins-Sussman (sussman@collab.net) wrote:
>
> Subversion has changesets, but they're sort of implicit. Each
> subversion commit *does* have a unique name -- the revision number.
> We can examine subversion's "changesets" by looking at the diff
> between any two revisions. We can also apply a "changeset N" to a
> working copy in any order by running 'svn merge -r N-1:N'.
This has two potential problems. The first is that I may be working
on a branch and doing various checkins before I wish to release the
finished entire set as one 'changeset' in its entirity.
The other issue is in the bundle. Patches generated with diffs get
corrupted in mail and are big and bulky and don't preserve change
history and the like.
What I think people are looking for from changesets is a URL that
you can give to someone who is managing a release and say
'my fix for the splurge bug is in http://myrepository/mychangeset...'
and then the release person (or whoever wants to try it) can do
svn magic http://myrepository/mychangeset
and when that happens it merges in the changeset, preferably keeping the
change history and a note to say that this changeset has been added to
the repository.
Dave
---------------- Have a happy GNU millennium! ----------------------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 8 21:59:07 2002