Originally created by: sa3ruby@gmail.com
Originally owned by: cmpilato
The premise of this issue is that people should not have to read an entire
book, including a section called Peg and Operative Revisions in a chapter
named Advanced Topics in order to correctly code an svn command in a script
they are writing. At a minimum, there should be a forward pointer to this
section.
Further background:
http://intertwingly.net/blog/2010/01/15/Peg-svn-revisions
Note: this is emphatically *not* a defect report about the need to append
an '@' to file names that may, themselves, contain '@' signs; or on the
incompatible API change that that represents -- I understand how such came
to be. But I do have a suggestion along those lines: if a peg revision is
specified and a file is skipped in the processing of a command then perhaps
an additional informational message can be produced suggesting that perhaps
an @ at the end of the command is needed? If that produces too many false
positives, then perhaps that could be further scoped down to purported peg
revisions that contain non-numeric characters. That may not help the
news@11 case, but would have helped in my case (the file names in question
were email addresses).
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cmpilato
(No comment was entered for this change.)
Labels: Milestone-en-1.6
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cmpilato
(No comment was entered for this change.)
Owner: cmpilato
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cmpilato
Pushing this off as not-strictly-needed-for-1.6-coverage. (Trying to get to the 1.7 work sooner rather than later.)
Labels: Milestone-en-1.7
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cmpilato
Add a much earlier mention of the at-syntax problem (to Chapter 1's "Addressing the Repository" section) in [r4011]. While that section is about the repository, it's "entry-level" enough that I suspect nearly everyone will read it.
Resolving this as "Fixed", but of course, Sam, if you want something better/different, feel free to reopen and suggest as much.
Status: Fixed
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cmpilato
Backported to the 1.6 version in [r4012].
Labels: -Milestone-en-1.7 Milestone-en-1.6