On Tue, Apr 19, 2016 at 09:58:36AM -0700, Ryan J Ollos wrote:
> The SVK project hasn't been developed since 2010, so it seems appropriate
> to remove mention of it as an alternative to SVN. Patch is attached.
>
> [[[
> Remove mention of SVK project as alternative in svnsync.txt
> ]]]
>
> - Ryan
Hi Ryan,
Since you have an apache.org account, you can just commit this.
We have enabled commit rights for all ASF committers in ^/subversion.
You can mention my approval in the commit message, if you like:
Approved by: stsp
But that's not mandatory. We also have an 'obvious fix' rule which
means everyone can commit trivial fixes like this without prior approval.
Just include the phrase 'obvious fix' in the commit message if you'd
like to invoke this rule.
For more information about conventions we use, such as our preferred
log message format, see our community guide:
http://subversion.apache.org/docs/community-guide/
Thanks!
> Index: svn-trunk/notes/svnsync.txt
> ===================================================================
> *** svn-trunk/notes/svnsync.txt (revision 1739958)
> --- svn-trunk/notes/svnsync.txt (working copy)
> *************** $ svnsync sync file://`pwd`/dest
> *** 152,160 ****
> was secretproject, only the changes starting from the revision in which the
> rename to project1 was committed will be synced.
>
> - If you need any of these abilities right now, you may want to look into SVK
> - (http://svk.bestpractical.com/).
> -
> Q: What happens when I change a revprop on the master server?
>
> A: That depends, did you change it on a revision that had already been
> --- 152,157 ----
Received on 2016-04-19 19:16:10 CEST