From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 3DD05384AB65 for ; Tue, 23 Apr 2024 15:45:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 3DD05384AB65 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 3DD05384AB65 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1713887142; cv=none; b=vfcm4gnqNOvnGmxZc4450nXPGnWYF+PdnxdLNkE0RJRiw+r5aUM89NQImC5eB3XbaUu4nwjcM+G6OgPH8yjN+xXmz0YN4TvtEB7Dcd0/Per8lXYV8QGFPDXL6zcZErKzXhg+QK+wKdifut6nxVQZ15JXaFo4XTMIc/2YG07Lq3o= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1713887142; c=relaxed/simple; bh=HwTB1LVoJoMmwTMgwgG0gtPC8eXMvHyYikOfF80nvWA=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=CWh/tyLkCv2AQBtwaPAqG/gG7lSWQzOY9Iv7NNA2Pc6eENQA1XWIbRIQtvRjClgy3LZOAusRRlHzKnn8o6pr6NfyJAf6gsugV7iUAhEIV2mWvtsp0H9xS6x6sOP7xfOSZdVy74mD7L7i0dH4ScsCyyrlhwaNzr+6JuBT4SvwXXA= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1713887139; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=2NAMVhff5DV4lyHwEBuZf5QG35lo0Rvb+Ye04ElbXOs=; b=UGRCPQrP5baPBDo3zi7XSbdFujMuG05sB3MW+AtHpOwNYuqrvJMtqAuusTnmAqMgjRUUqz df3+MwAHnsVPo1Z2U9/EzuMLHb64tCdO0j+P+iQ1kYOH2lZ54EEUfRq/wYZQjXAyLLtc72 cOG7qD0bqhKpuFRV+LYfZKycle8qAG4= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-307-0cEFYZnNNPSKaoJJwKZP3A-1; Tue, 23 Apr 2024 11:45:38 -0400 X-MC-Unique: 0cEFYZnNNPSKaoJJwKZP3A-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id DABF8104D50A for ; Tue, 23 Apr 2024 15:45:37 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.45.224.5]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 655F42166B31; Tue, 23 Apr 2024 15:45:37 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 43NFjZhg932818 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Tue, 23 Apr 2024 17:45:35 +0200 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 43NFjZ3Z932817; Tue, 23 Apr 2024 17:45:35 +0200 Date: Tue, 23 Apr 2024 17:45:35 +0200 From: Jakub Jelinek To: David Malcolm Cc: Mark Wielaard , gcc-patches@gcc.gnu.org Subject: Re: [PATCH] DOCUMENTATION_ROOT_URL vs. release branches [PR114738] Message-ID: Reply-To: Jakub Jelinek References: MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-3.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Tue, Apr 23, 2024 at 11:40:55AM -0400, David Malcolm wrote: > > So, I think at least for the MAJOR.MINOR.0 releases we want to use > > URLs like above rather than the trunk ones and we can use the same > > process > > of updating *.opt.urls as well for that. > > Would it make sense to instead update the default value in > gcc/configure.ac for DOCUMENTATION_ROOT_URL when branching or > releasing, from https://gcc.gnu.org/onlinedocs/ to > https://gcc.gnu.org/onlinedocs/gcc-MAJOR-MINOR.0/ > > ? > > Before this patch the DOCUMENTATION_ROOT_URL expresses the location of > a built texinfo html tree of docs, and the url suffixes express the > path within that tree. > > As the patch is written, if a distributor overrides --with- > documentation-root-url= at configure time, then they need to mirror the > structure of our website on their website, which seems like a burden. Sure, that is doable (of course, it shouldn't be done by updating gcc/configure.ac but by adjusting the default in there based on gcc_version, I'll post a patch tomorrow). Still, what do you think we should do on the release branches (recommend to developers and check with the post-commit CI)? No regeneration of *.urls except before doing a new release candidate, or a different make goal that would grab html files from the web and regenerate against that? Jakub