From patchwork Sat Jan 12 16:27:32 2019
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Gerald Pfeifer
X-Patchwork-Id: 1023922
Return-Path:
X-Original-To: incoming@patchwork.ozlabs.org
Delivered-To: patchwork-incoming@bilbo.ozlabs.org
Authentication-Results: ozlabs.org;
spf=pass (mailfrom) smtp.mailfrom=gcc.gnu.org
(client-ip=209.132.180.131; helo=sourceware.org;
envelope-from=gcc-patches-return-493932-incoming=patchwork.ozlabs.org@gcc.gnu.org;
receiver=)
Authentication-Results: ozlabs.org;
dmarc=none (p=none dis=none) header.from=pfeifer.com
Authentication-Results: ozlabs.org; dkim=pass (1024-bit key;
unprotected) header.d=gcc.gnu.org header.i=@gcc.gnu.org
header.b="buB4SN9K"; dkim-atps=neutral
Received: from sourceware.org (server1.sourceware.org [209.132.180.131])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
bits)) (No client certificate requested)
by ozlabs.org (Postfix) with ESMTPS id 43cQBW4gZ4z9rxp
for ;
Sun, 13 Jan 2019 03:27:44 +1100 (AEDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gcc.gnu.org; h=list-id
:list-unsubscribe:list-archive:list-post:list-help:sender:date
:from:to:subject:message-id:mime-version:content-type; q=dns; s=
default; b=sJRRSESDDf0oB4uDI7NwQONzWP9WLz+xt41HlvYdP4qzVABvRDJMb
CXRbHv2C0eO+So7PsktTlpF0UTb4l8ShBCRj/lnZnjeiWnjCywdBQKerkXFhwoPm
A99r9pMpYmOwoyM/VjJS53CSN14yFFAVVKilIi4LVXivH4ZFMpU3WQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gcc.gnu.org; h=list-id
:list-unsubscribe:list-archive:list-post:list-help:sender:date
:from:to:subject:message-id:mime-version:content-type; s=
default; bh=yfpVI0SfFpy6A2fCw0uJlERIMYo=; b=buB4SN9KTCrW9F6WwD+O
Ki8CFX/0oAxh2bKQVVj4pAwWbM3vbJJ3ub+cleoK4p6GBWMn0UFOQ5qC6gtDxVSb
HHcp2SoXUh/f/Op6NLN6nAkFoOCk6a9N3jBmSIA/i4hBPPAByNO+VfW+2seczkGx
3FTavKiIRzBgI01f1wTZK/k=
Received: (qmail 119079 invoked by alias); 12 Jan 2019 16:27:38 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id:
List-Unsubscribe:
List-Archive:
List-Post:
List-Help:
Sender: gcc-patches-owner@gcc.gnu.org
Delivered-To: mailing list gcc-patches@gcc.gnu.org
Received: (qmail 119067 invoked by uid 89); 12 Jan 2019 16:27:37 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-11.2 required=5.0 tests=BAYES_00, GIT_PATCH_2,
GIT_PATCH_3,
SPF_SOFTFAIL autolearn=ham version=3.3.2 spammy=accidental,
Hx-languages-length:1681, svn, Perhaps
X-HELO: hamza.pair.com
Received: from hamza.pair.com (HELO hamza.pair.com) (209.68.5.143) by
sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP;
Sat, 12 Jan 2019 16:27:36 +0000
Received: from hamza.pair.com (localhost [127.0.0.1]) by hamza.pair.com
(Postfix) with ESMTP id 85F0D33F55 for ;
Sat, 12 Jan 2019 11:27:34 -0500 (EST)
Received: from [192.168.43.3] (ip-109-41-192-55.web.vodafone.de
[109.41.192.55]) (using TLSv1.2 with cipher
ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client
certificate requested) by hamza.pair.com (Postfix) with
ESMTPSA id 0F82D33F52 for ;
Sat, 12 Jan 2019 11:27:33 -0500 (EST)
Date: Sat, 12 Jan 2019 17:27:32 +0100 (CET)
From: Gerald Pfeifer
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] svnwrite.html - reduce references to SVN
Message-ID:
MIME-Version: 1.0
X-IsSubscribed: yes
When migrating from CVS to SVN I already reduced direct references
to CVS/SVN, and expecting a migration to GIT in this decade let me
take the opportunity to generalize/simplify things a bit further.
Committed.
(Perhaps we should also start refering to the more general term
"commit" vs "check in"?)
Gerald
Index: svnwrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v
retrieving revision 1.42
diff -u -r1.42 svnwrite.html
--- svnwrite.html 30 Sep 2018 14:38:47 -0000 1.42
+++ svnwrite.html 12 Jan 2019 16:23:09 -0000
@@ -142,7 +142,7 @@
Free for all
-The following changes can be made by everyone with SVN write access:
+The following changes can be made by everyone with write access:
Obvious fixes can be committed without prior approval. Just check
in the fix and copy it to gcc-patches
. A good test to
@@ -207,13 +207,12 @@
when performing checkins to avoid accidental checkins of local
code.
-We prefer that each SVN checkin be of a complete, single logical
+
We prefer that each checkin be of a complete, single logical
change, which may affect multiple files. The log message for that
checkin should be the complete ChangeLog entry for the change. This
makes it easier to correlate changes across files, and minimizes the
time the repository is inconsistent. If you have several unrelated
-changes, you should check them in with separate SVN commit
-commands.
+changes, you should check them in separately.
- Sync your sources with the master repository via "
svn