public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Gary V. Vaughan" <gary@gnu.org>
To: "overseers@sourceware.org" <overseers@sourceware.org>,
	"sourcemaster@sourceware.org" <sourcemaster@sourceware.org>
Cc: Ben Elliston <bje@air.net.au>, Ian Lance Taylor <ian@airs.com>,
	"tom@tromey.com" <tom@tromey.com>
Subject: Re: autobook?
Date: Wed, 27 May 2015 21:52:00 -0000	[thread overview]
Message-ID: <70268AE1-4A64-4662-A377-944317395969@gnu.org> (raw)
In-Reply-To: <20150527212558.GA27090@air.net.au>

Dear sourceware,

We, the authors of the goat book you have kindly hosted for us this past decade
and a half cannot remember where to upload the html pages served from

     http://sourceware.org/autobook/autobook/autobook.html.

Please remind us of the process so we can update to a GFDL license, and
hopefully, begin to modernize the content to reflect latest autotools...

> On 27 May 2015, at 22:25, Ben Elliston <bje@air.net.au> wrote:
> 
> Hi Gary

Hello Ben \o

>>   cvs commit
> 
> OK, my memory isn't that bad. :-)

Well, we're all 15 years older than we used to be... :-p

Thanks for taking care of this by the way!

> I am referring to the HTML version
> of the book, located here:
> 
> https://sourceware.org/autobook/autobook/autobook.html
> 
> Where does the web server pick these files up from?  How do we update
> them?  There is an 'htdocs' directory in the source tree, but it's
> empty.

I seem to recall copying them to another repo and committing that. But my
laptop only has the sources working dir, so that could easily be a false
memory.

There are some contact email addresses on the sourceware front page, so
I guess we'll need to ask there for a reminder... I've addressed this
message to them.

> Cheers, Ben

Cheers,
-- 
Gary V. Vaughan (gary AT vaughan DOT pe)

       reply	other threads:[~2015-05-27 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1YqnJg-0003hx-7F@fencepost.gnu.org>
     [not found] ` <m3vbg1923e.fsf@pepe.airs.com>
     [not found]   ` <E1YrT87-0000dg-5A@fencepost.gnu.org>
     [not found]     ` <m3twv02d7s.fsf@pepe.airs.com>
     [not found]       ` <E1YxDSM-0001nY-SU@fencepost.gnu.org>
     [not found]         ` <20150527072519.GB15973@air.net.au>
     [not found]           ` <20150527073442.GA16438@air.net.au>
     [not found]             ` <F2F72453-0F84-42BF-A54D-DDB3CECE87DE@gnu.org>
     [not found]               ` <20150527212558.GA27090@air.net.au>
2015-05-27 21:52                 ` Gary V. Vaughan [this message]
2015-05-27 22:19                   ` autobook? Frank Ch. Eigler

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=70268AE1-4A64-4662-A377-944317395969@gnu.org \
    --to=gary@gnu.org \
    --cc=bje@air.net.au \
    --cc=ian@airs.com \
    --cc=overseers@sourceware.org \
    --cc=sourcemaster@sourceware.org \
    --cc=tom@tromey.com \
    /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).