Hello, On Sat, Sep 30, 2017 at 1:41 AM, Johan Corveleyn <[email protected]> wrote: > On Wed, Sep 27, 2017 at 5:08 PM, Pavel Lyalyakin > <[email protected]> wrote: >> Hello Johan, >> >> Thank you for taking the time to review this patch. :) >> >> I think that I addressed most of your comments and suggestions in the >> attached patch svn-updated-quick-start-v3.patch.txt. I've attached an >> interdiff to v2 patch, too. > > That's all looking great, Pavel, nice work.
Thanks for the review. :) > [snip] > >> Sure, I am going to continue with this task. The current version of >> the document (as it is in v3 patch) is missing several important >> sections that I thing about adding: >> * Viewing the history of changes: provide `svn log` examples. >> * Merging: automatic reintegration merges and cherry-picking. >> * Tagging: we should provide tagging examples. >> * Creating your own local repository: a quick guide on this task with >> a link to SVNBook's High-Speed Tutorial. > > I'd like to commit your current v3 patch, so we already have this in > place. Further improvements can then happen in followup patches / > commits. Unless you prefer to make it more complete before committing > anything? I don't see a reason myself to hold back and make > incremental improvements later, but I'll wait for you to let me know > what you prefer. Sure, please, commit v3 patch. It will help me divide further work into atomic patches or commits instead of a single blanket patch. I'm sure that it will be much easier to review the document this way. I am going to work on further improvements and as soon as they are ready, I will start a new [PATCH] thread. However, what about creating a lightweight branch[1] for this doc task? I know that a lightweight branch can be created for code changes, but the site/ does not have branches at all. I am not sure about that. [1]: http://subversion.apache.org/docs/community-guide/general.html#lightweight-branches -- With best regards, Pavel Lyalyakin VisualSVN Team
