Return-Path: X-Original-To: apmail-subversion-dev-archive@minotaur.apache.org Delivered-To: apmail-subversion-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5A1FB1955E for ; Tue, 19 Apr 2016 17:16:08 +0000 (UTC) Received: (qmail 29146 invoked by uid 500); 19 Apr 2016 17:16:08 -0000 Delivered-To: apmail-subversion-dev-archive@subversion.apache.org Received: (qmail 29088 invoked by uid 500); 19 Apr 2016 17:16:08 -0000 Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@subversion.apache.org Received: (qmail 29074 invoked by uid 99); 19 Apr 2016 17:16:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2016 17:16:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C49B3C12F3; Tue, 19 Apr 2016 17:16:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.699 X-Spam-Level: X-Spam-Status: No, score=-0.699 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_LOW=-0.7, UNPARSEABLE_RELAY=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 4ujoOX6gIFco; Tue, 19 Apr 2016 17:16:05 +0000 (UTC) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 5844F5F610; Tue, 19 Apr 2016 17:16:05 +0000 (UTC) X-Envelope-From: stsp@apache.org Received: from ted.stsp.name (ted.stsp.name [217.197.84.34]) by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id u3JHFwK0003397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 19 Apr 2016 19:15:59 +0200 Received: from localhost (ted.stsp.name [local]) by ted.stsp.name (OpenSMTPD) with ESMTPA id 2abf3ae4; Tue, 19 Apr 2016 19:15:58 +0200 (CEST) Date: Tue, 19 Apr 2016 19:15:58 +0200 From: Stefan Sperling To: Ryan J Ollos Cc: dev@subversion.apache.org Subject: Re: [PATCH] Remove mention of SVK in svnsync.txt Message-ID: <20160419171558.GB16494@ted.stsp.name> Mail-Followup-To: Ryan J Ollos , dev@subversion.apache.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) 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 ----