linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] CVS not updated?
Date: Fri, 28 May 2004 21:09:18 +0200	[thread overview]
Message-ID: <200405282109.18920.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20040523214437.GC25780@ccure.user-mode-linux.org>

> > I would suggest to write, on the server, a script which checks out
> > everything from the CVS repository and rebuilds it; then you commit the
> > new site, run the script from the server and it should work perfectly +
> > the site would always be up-to-date.
>
> That would require leaving my private key on the UML, which doesn't sound
> like such a hot idea.  Although I could make a "uml-dev" key pair, which I
> use instead.  Plus, I could put it anywhere uml-dev privs are needed, and
> you could use it as well.

Why do you need a private key anywhere? The checkout should be done with 
pserver (i.e. anonymous CVS); checkout + rebuild should be done on the 
web-server. The private key is needed only by who writes something in the 
repo, i.e. you and who you want; obviously public key must be stored in 
authorized_keys but that is NOT a problem.

Bye
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-05-28 19:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 15:51 [uml-devel] CVS not updated? Henrik Nordstrom
2004-05-17 17:02 ` Henrik Nordstrom
2004-05-17 18:59   ` Henrik Nordstrom
2004-05-17 20:00     ` roland
2004-05-17 21:14       ` Henrik Nordstrom
2004-05-17 22:04         ` roland
2004-05-17 22:05           ` Henrik Nordstrom
2004-05-18 18:02             ` Jeff Dike
2004-05-18 19:42               ` Henrik Nordstrom
2004-05-18 22:00                 ` Jeff Dike
2004-05-18 21:38                   ` roland
2004-05-23 11:37                   ` BlaisorBlade
2004-05-23 16:44                     ` Henrik Nordstrom
2004-05-24 17:44                       ` BlaisorBlade
2004-05-27 18:21                         ` Henrik Nordstrom
2004-05-23 21:44                     ` Jeff Dike
2004-05-28 19:09                       ` BlaisorBlade [this message]
2004-05-28 21:33                         ` Jeff Dike

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=200405282109.18920.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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