On Wed, 2004-02-18 at 11:22, Marcin Kasperski wrote:
> (page 50, note about running svn log in my-calc-branch)
> I doubt whether after merging the branch changes to the trunk,
> the commit message will be visible in the branch log. It seems
> to me that it is the trunk that changed, on the branch nothing
> has changed and nothing has been commited.
Holy cow, that was a huge brain-o. Thank you for spotting that! All
fixed. That example is supposed to be running log on the trunk, indeed.
> (page 31, resolving sandwich.txt by copying sandwich.txt.r2 and
> running svn resolved)
> What are we commiting here? It seems we have nothing to commit as
> nothing has changed comparing to the repository.
Another good catch, thanks. Removing that last commit line.
> (page 41, introduction to branching with branches dir)
> I would add here a mention (likely a footnote) that there exists
> a method (svn switch) which allow one to keep the same working
> dir while moving from trunk to branch and opposite.
We cover that later in the chapter... a whole section dedicated to svn
switch. I think that mentioning switch in the very beginning of the
chapter would be too much information.
> (chapter 4)
> I would probably introduce tags first, branches and merges later.
> Maybe my CVS habits makes me to think so but tags are simpler
> concept. Moreover, I would either change chapter 4 title to
> 'Branching, Merging and Tagging' or move tagging description to
> separate chapter.
This is a deliberate choice, actually. The "hard concept" is the idea
of making a cheap copy. I want people to think of branches as normal
copies, and tags as copies that don't change. So I introduce the copy
concept first, show how it's useful for branching, then describe tagging
as a secondary use of copying.
> I would introduce early in the book and use consistently some
> method of avoiding urls in the commands. Maybe
> export SVNREP='http://my.repo.com/subversion'
> svn checkout $SVNREP/mymodule
> maybe something else....
Why? Most people only do that sort of thing when they're about to
execute 20 commands that require the same $SVNREP prefix. It's pretty
uncommon to *ever* have to type a url in day to day work. This
technique is more useful for scripts that do automated repository access
with no working copies available.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Feb 18 19:43:14 2004