From: Nick Clifton <nickc@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: joel@rtems.org, Mike Frysinger <vapier@gentoo.org>,
Joel Brobecker <brobecker@adacore.com>,
Nick Clifton via Binutils <binutils@sourceware.org>
Subject: Re: A GNU Binutils wiki
Date: Wed, 30 Nov 2022 11:03:12 +0000 [thread overview]
Message-ID: <4944644e-68c3-abfa-e2dd-e99bcb4085f0@redhat.com> (raw)
In-Reply-To: <Y4P2XBU8LxkyyScE@wildebeest.org>
Hi Mark,
>> Would you feel happier if the text for the wiki was kept in the sources
>> and then uploaded to the site on a semi-regular basis ?
> How are the current code snapshots created?
I think that there is a cron job on sourceware that creates the snapshots.
> How is the documentation uploaded at release time?
By hand. :-)
I have a procedure outlined in the binutils/README-how-to-make-a-release
document that I follow whenever I need to update the documentation.
> We can automate both and publish them on a special buildbot worker
> under something like snapshots.sourceware.org/bintuils to keep them
> current and so everybody can immediately see how the documentation
> looks.
That would be nice. Would it involve taking up a lot of disk space ?
(Ie for how long would these snapshots last ?)
Cheers
Nick
next prev parent reply other threads:[~2022-11-30 11:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 13:34 Nick Clifton
2022-11-01 13:44 ` Joel Brobecker
2022-11-01 15:17 ` Mike Frysinger
2022-11-01 16:47 ` Nick Clifton
2022-11-02 10:34 ` Mike Frysinger
2022-11-02 13:41 ` Joel Sherrill
2022-11-02 14:49 ` Nick Clifton
2022-11-02 15:04 ` Joel Brobecker
2022-11-02 15:12 ` Joel Sherrill
2022-11-27 23:44 ` Mark Wielaard
2022-11-30 11:03 ` Nick Clifton [this message]
2022-12-31 22:19 ` Mark Wielaard
2023-01-03 10:08 ` Nick Clifton
2022-11-02 15:28 ` Luis Machado
2022-11-09 17:00 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4944644e-68c3-abfa-e2dd-e99bcb4085f0@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=joel@rtems.org \
--cc=mark@klomp.org \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).