From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) by sourceware.org (Postfix) with ESMTPS id 023F33858403 for ; Thu, 25 Nov 2021 02:00:52 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 023F33858403 Received: by mail-wm1-x333.google.com with SMTP id i12so4156733wmq.4 for ; Wed, 24 Nov 2021 18:00:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=6e5ejGdTs4SWi/bfhHvT288LeBJ/V00ewjDKq01adAA=; b=ksXwCuzSFrgdUMR7zOLIpf7v7Vp+qzVtU8JkH3Nq3DK2zgVPUHsVv63rBTuPGenq5C Ks2SeeIN5v+pEPwNLcmEaJ+KP7+50pRPzu/T4s4Gz/vBlaByDTPoGhlqFdnPvnYa29Gs ABI8Tb0hg5lEaCHqHYseM8oszpW7YJ2RpluZwQM7PajB/bDJR9QE3lbuNJ3QSX191BVm SyJ5Hud7helZfTJOGrvCkbRGbbH0E13EURTiSX3wWYW8Cf2LMSzole+q8wM8jsHb0mEA +93APo92mimpUvnsR6Fyh+FyxNjDioUzRco/N24+YNNRaGvMVuNU4C2iyKxjBf+M5mX8 4//A== X-Gm-Message-State: AOAM533rzHBUwPY2//GLYsRC0hQzVhF3tWaZP9cdpuKAdxNh5uCXk6Yc 9ZWizQcMIq8U4nitD8GUZueW X-Google-Smtp-Source: ABdhPJyZD5HszJFLi+r52zbGRHf221HYqV2FzjTX6uaTTTHOPjpa5cRr6CjdCJ6HzTPvsnxDtgX7mQ== X-Received: by 2002:a05:600c:4fc3:: with SMTP id o3mr2366314wmq.147.1637805651007; Wed, 24 Nov 2021 18:00:51 -0800 (PST) Received: from takamaka.home ([2a01:cb22:1d5:1100:506c:df36:e6f3:e00f]) by smtp.gmail.com with ESMTPSA id ay29sm1239422wmb.44.2021.11.24.18.00.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 24 Nov 2021 18:00:50 -0800 (PST) Received: by takamaka.home (Postfix, from userid 1000) id DC8D6A4A7B; Thu, 25 Nov 2021 06:00:47 +0400 (+04) Date: Thu, 25 Nov 2021 06:00:47 +0400 From: Joel Brobecker To: Mark Wielaard Cc: Joel Brobecker , Pedro Alves , Overseers mailing list , simon.marchi@polymtl.ca, eliz@gnu.org, Mike Frysinger Subject: Re: setting up sim project web space Message-ID: References: <6a72ecd6-1480-1cb8-c223-c6c9d991be2e@palves.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-3.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2021 02:00:54 -0000 Hi Mark, > > The GDB website is under CVS, and there are two copies. > > > > - One is hosted on GNU Savannah > > https://savannah.gnu.org/projects/gdb > > This is the source of the website that's published on gnu.org: > > https://www.gnu.org/software/gdb/ > > For savannah you are unfortunately stuck with CVS for webpages. But you > can just install a redirect to https://sourceware.org/gdb/ so you don't > need to keep mirroring it in two places. Sounds like an interesting idea. One of the things I'm concerned about is perhaps people having bookmarks of old pages. Or perhaps have every one of the current pages be a redirect to the corresponding page? Something like this? Redirecting to

Redirecting to sourceware.org

> > - One is hosted on sourceware.org > > CVS/Root: sourceware.org:/cvs/gdb > > CVS/Repository: htdocs > > > > This repository is the source of the copy on sourceware.org: > > https://www.sourceware.org/gdb/ > > > > I don't know why we have two copies of the website, unfortunately. > > > > It would be nice if we could transition the sources to Git. > > I haven't done it, because I don't know how the automatic-update-after-push > > is set up, so I'm concerned about breaking the website update if I do. > > Sadly my knowledge of CVS is fairly minimal at this point, so I don't > really understand fully how it is setup now. But I can see that it > involves getting a checkout under > /sourceware/www/sourceware/htdocs/gdb/ > I can convert the CVS repo to git and then setup the git hooks to do > the same. Combined with the redirect, I think this would be great. > That does leave the question of who should be in the gdb group (and is > allowed to push) and how the onlinedocs are updated, those under: > https://sourceware.org/gdb/current/onlinedocs/ > Which seems to be done by some script and you need to be in the > "shared" group to be able to put files there. For the onlinedocs part, it's user "gdbadmin" who does those updates. It does so nightly via crontab. For the permissions to push to the new htdocs, I can ask the question to the GDB Global Maintainers. Perhaps they'll agree that anyone allowed to push to GDB can also push to GDB's htdocs, particularly if we set the git-hooks up so as to have commit emails sent to gdb-cvs. > > Meanwhile, because I've pretty much been the only editor of those > > sources, I've been able to get away with my own Git repository and > > the use of "git cvsexportcommit" to push patches. > > > > If people send me patches, I'm happy to push them. > > Does that include the sim manuals that started this thread? Sure. > It seems better to get things moved to git and make it possible for > others to also update the gdb webpages. Let me know if I can help with > that and who should be involved to make sure we update all automated > scripts. Agreed. -- Joel