From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: fix typo on web page
Date: Wed, 03 Dec 2008 16:29:00 -0000 [thread overview]
Message-ID: <m3myfd8br0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20081127004018.GA3768@adacore.com> (Joel Brobecker's message of "Wed\, 26 Nov 2008 16\:40\:18 -0800")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> Thanks for the fix. And welcome to be Royal Pain of the GDB Web Site:
Joel> All pages have a "last modified" line at the end that gets automatically
Joel> updated if you call the "index.sh" script (at the root).
Sorry about the mess.
I could automate the index.sh part if you like.
We could do this as a post-processing step on the server, say by
renaming index.html -> index.in, and then having a little Makefile.
What do you think?
Joel> Once the updates are checked in, the sourceware.org copy will
Joel> immediately show your changes. But there is another copy at gnu.org
Joel> (http://www.gnu.org/software/gdb/). To update that copy, you have
Joel> to check out a second CVS (yes, a second one), and then copy over
Joel> the new files, and check them in.
Ugh. I think GCC automates this sync, too, but I don't know how.
We could find out.
Joel> If I was less lazy and Web updates were more frequent than they
Joel> currently are, I'd probably try to work on the issues above...
The variables aren't independent; web updates may be rare because they
are difficult. E.g., I prefer the wiki since it isn't nearly such a
pain, especially now that I know exactly how much of a pain it is ;-)
Tom
prev parent reply other threads:[~2008-12-03 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 15:01 Tom Tromey
2008-11-27 15:23 ` Tom Tromey
2008-11-27 16:54 ` Daniel Jacobowitz
2008-11-27 17:17 ` Joel Brobecker
2008-12-03 16:29 ` Tom Tromey [this message]
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=m3myfd8br0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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