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

Re: Beta or RC by Wednesday evening

From: Augie Fackler <durin42_at_gmail.com>
Date: Thu, 13 Mar 2008 10:28:48 -0500

Ben Collins-Sussman wrote:
> On Wed, Mar 12, 2008 at 1:05 PM Karl Fogel <kfogel_at_red-bean.com>
> wrote:
> > The most important place to do this is the release notes. The book
> > should also do it a bit but that has to be carefully worded because
> > some of those missing features will be implemented during the time
> the
> > book is still in print.
> I've tried to do this in chapter 4 but I'd very much love feedback
> from anyone who has time to do a 'casual read' of the chapter from
> the point of view of a novice.

I ran the book by a coworker here who doesn't have any experience with
svn 1.5, here's what he had to say:
---------------
Very cool. A couple of notes - not much, I know:

> svn.branchmerge.using.html - The section 'branches are cheap' is
> really quite excellent. I always knew they were 'cheap' but had
> never really dived into why.

> svn.branchmerge.basicmerging.html - 'svn merge --reintegrate', very
> cool.

> svn.branchmerge.advanced.html - I would really make the 'word of
> warning' section more prominent. It seems to me that that section is
> valuable enough that more attention should be called to it. The
> section starts with: 'A word of warning: while svn diff and svn
> merge are very similar in concept, they do have different syntax in
> many cases.'

In general the 'svn switch' command and concept still escapes me. I
think the text does a fine job of explaining its behavior in the
context of 'svn update' but I still don't get it.

Aside from that - I'm excited for 1.5.
--------------

Hope that helps everyone out a bit.
Augie

  • application/pkcs7-signature attachment: smime.p7s
Received on 2008-03-13 16:29:07 CET

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.