1 |
On Friday 11 March 2005 02:06, Martin Schlemmer wrote: |
2 |
> On Thu, 2005-03-10 at 20:19 +0200, Dan Armak wrote: |
3 |
> > On Thursday 10 March 2005 18:12, Aaron Walker wrote: |
4 |
> > > http://dev.gentoo.org/~ka0ttic/tmp/svn-glep.txt |
5 |
> > > |
6 |
> > > comments? |
7 |
> > |
8 |
> > I'm a fan of subversion. Hosted an ebuild overlay (the original kde split |
9 |
> > ebuilds) at berlios.de because we only had cvs. So I'm obviously glad to |
10 |
> > see this :-) |
11 |
> |
12 |
> Big yes here too. |
13 |
> |
14 |
> > You write that subversion supports changesets, but AFAIK it doesn't, and |
15 |
> > the Subversion Book seems to confirm this. What exactly do you mean by |
16 |
> > changesets? I'm not sure what changesets are myself, but fex. there's no |
17 |
> > SVN format for describing a commit's contents (properties, moves, ...) |
18 |
> > which can be applied to a working copy (as svn merge would). |
19 |
> |
20 |
> Hrm, I would like this cleared up as well, as I also was made to think |
21 |
> it could ... |
22 |
Looking at the svn docs again, they call the changes made by a revision a |
23 |
changeset. But they do make the point that what I described above is |
24 |
impossible - IOW svn merge can't accept output to a file, and svn diff only |
25 |
outputs the info an ordinary diff does. svn also can't track these changesets |
26 |
when porting between branches (arch is supposed to be good at this) - the |
27 |
docs advise you to put 'ported rev X from branch Y' as the commit message |
28 |
when porting. |
29 |
|
30 |
So svn does support what they call 'changesets' - but in svn parlance, |
31 |
changesets don't really mean anything... |
32 |
|
33 |
-- |
34 |
Dan Armak |
35 |
Gentoo Linux developer (KDE) |
36 |
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key |
37 |
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD 0069 508D 9143 8D5F 8951 |