From owner-freebsd-stable@freebsd.org Wed Feb 17 17:56:46 2021 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A03D454C9C0 for ; Wed, 17 Feb 2021 17:56:46 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-il1-f172.google.com (mail-il1-f172.google.com [209.85.166.172]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Dgls92Y19z4Rmq for ; Wed, 17 Feb 2021 17:56:45 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-il1-f172.google.com with SMTP id o7so12082018ils.2 for ; Wed, 17 Feb 2021 09:56:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=khGACJLNAbSm3ypW8jlyHWvYE6G3Y/pYGRFR9YEMTho=; b=b9PV+SwZJrnURVAEqxCsC1v5g717CK+zAai+qWputSu/DbqgmqPtufHHbTHF1wFokn /+YXNdHGCaC+u+6MgkL2BF//NuwjG9Trv03Khy+UQSRcgLHEaGX8wYUrMGRg0GjOjZj0 Tonn9pEf8ZGS0ZMDEPblJu/EhpnKG2Jh4H78oEVahvpNTMj4CDHSjhLcXihATATMLtOK 4yLeTFq0It2IttSwygvSPN/ZcChGhg/7MQe1ZpJvYjEgpif6gB/f6SloEbzyRnELZiYJ g7cE3FC2KowSZ36Bfq4rc35S6S+O0gL+ga8zw/WH2Kgdu6W+Pn4gg85XM2fKrhnaafVB mg2A== X-Gm-Message-State: AOAM532HUd0SSejutXakXubEE1IcqS3Icwq6VmSOWw0+PfoIvzPXlRzx pSx6nIwZXJgKWfAd9BLLyMItZpgG67qRGrej4sagFg0dWB4= X-Google-Smtp-Source: ABdhPJzUQsS7TB5Tsf7s3at83KTDiy7oGpWlq6GKiC/7yJWVspwVi+cuBm/w7nSwTc7qeVOxlLI7l8YPy4NGhD6QasE= X-Received: by 2002:a05:6e02:1bee:: with SMTP id y14mr223826ilv.256.1613584603469; Wed, 17 Feb 2021 09:56:43 -0800 (PST) MIME-Version: 1.0 References: <19D1F98B-6F55-42C7-9C82-FB6F6032EA66.ref@yahoo.com> <19D1F98B-6F55-42C7-9C82-FB6F6032EA66@yahoo.com> In-Reply-To: From: Ed Maste Date: Wed, 17 Feb 2021 12:56:03 -0500 Message-ID: Subject: Re: where to upgrade 12-stable now, svn still, or git? To: freebsd-stable stable Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4Dgls92Y19z4Rmq X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.172 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.166.172:from]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[carpeddiem]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[209.85.166.172:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.172:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.172:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-stable] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Feb 2021 17:56:46 -0000 On Fri, 12 Feb 2021 at 23:11, tech-lists wrote: > > I saw on cgit that stable/12 was there. These older systems weekly > update their sources via svn till now, in a cron job. At the time I wrote > my message, I saw that svn still works, so was wondering which to use, > which has the latest updates. You can continue to use svn for these as long as stable/12 is supported. The git-svn conversion script was set up explicitly to support this use case, and will remain in operation at least until stable/12's EOL. Security updates for stable/12 and 12.x releases will also be available via svn, and the advisories reference the svn revision.