all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] website: Add support for Haunt.
Date: Sat, 07 Nov 2015 12:04:14 +0100	[thread overview]
Message-ID: <87vb9e6pg1.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=RwfZBAQE1G1vkkpv7puUwaT2WwpfREu9c=6dqmsxc5TTuHQ@mail.gmail.com> (David Thompson's message of "Fri, 6 Nov 2015 15:58:56 -0500")

"Thompson, David" <dthompson2@worcester.edu> skribis:

> On Fri, Nov 6, 2015 at 3:47 PM, Ludovic Courtès <ludo@gnu.org> wrote:

[...]

>>> WARNING: Haunt builds the site afresh at each 'haunt build' run, which
>>> means that it deletes everything in the build directory first.  Will
>>> that be an issue here?
>>
>> That should be fine.
>
> OK.  I was worried that maybe some "stateful" stuff like the manual
> html pages would get clobbered or something.

Ah yes, that would be a problem.  It thought you were only talking about
the files that Haunt generates.

Currently, there’s a bunch of files that are only in CVS, such as the
PDFs of talks and the manual.  This is not ideal, but I’m not sure how
to address that.

Thanks,
Ludo’.

  reply	other threads:[~2015-11-07 11:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 21:26 [PATCH] website: Add support for Haunt Mathieu Lirzin
2015-11-03 23:21 ` Thompson, David
2015-11-04  0:21 ` Daniel Pimentel
2015-11-05 21:25 ` Ludovic Courtès
2015-11-05 21:48   ` Thompson, David
2015-11-05 23:50     ` Mathieu Lirzin
2015-11-06 14:28       ` Thompson, David
2015-11-06 15:11         ` Luis Felipe López Acevedo
2015-11-06 20:47     ` Ludovic Courtès
2015-11-06 20:58       ` Thompson, David
2015-11-07 11:04         ` Ludovic Courtès [this message]
2015-11-09 19:09           ` Thompson, David
2015-11-10 12:17 ` Alex Vong
2015-11-10 16:37   ` Mathieu Lirzin
2015-11-11  5:14     ` Alex Vong
2015-11-16 23:45       ` Mathieu Lirzin

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=87vb9e6pg1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.