From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Call for volunteer(s) for Guix "security" web page
Date: Thu, 29 Sep 2016 11:04:55 -0400 [thread overview]
Message-ID: <20160929150455.GA29138@jasmine> (raw)
In-Reply-To: <20160927182653.GK2569@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
On Tue, Sep 27, 2016 at 02:26:53PM -0400, Leo Famulari wrote:
> > Note that you’ll then need to commit the resulting HTML to CVS(!) to
> > that the update pages show up, as per the instructions available on the
> > Savannah project page. If you’re unsure or anything, I can do that.
>
> I'll try it if this new patch is okay.
I read some parts of the CVS manual [0].
I checked out the CVS repo over SSH as directed by Savannah. Then, I
copied all the new and changed files created by (export-web-site) in to
the CVS tree.
I want some reassurance that I'm doing the right thing before I do it :)
My plan:
$ cvs add security # The manual says that `cvs add` is not recursive.
$ cvs add security/index.html
$ cvs commit # I think this will commit all changes in tracked files.
Does that look right?
[0] For some reason nongnu.org/cvs directs users to archive.org for the
manual...
https://web.archive.org/web/20130202033128/http://ximbiot.com/cvs/manual/cvs-1.12.13/cvs_7.html#SEC68
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-29 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 16:14 Call for volunteer(s) for Guix "security" web page Leo Famulari
2016-09-22 10:04 ` ng0
2016-09-27 18:04 ` Leo Famulari
2016-09-25 22:52 ` Leo Famulari
2016-09-27 8:58 ` Ludovic Courtès
2016-09-27 18:16 ` Leo Famulari
2016-09-28 21:08 ` Ludovic Courtès
2016-09-27 18:26 ` Leo Famulari
2016-09-28 21:07 ` Ludovic Courtès
2016-09-29 15:04 ` Leo Famulari [this message]
2016-09-30 12:08 ` Ludovic Courtès
2016-09-30 18:06 ` Leo Famulari
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=20160929150455.GA29138@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@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.