From: Ingo Schwarze <schwarze@usta.de>
To: Guy Harris <guy@alum.mit.edu>
Cc: discuss@mdocml.bsd.lv
Subject: Re: Command-line anonymous CVS access to check out the repository?
Date: Wed, 13 Aug 2014 02:06:33 +0200 [thread overview]
Message-ID: <20140813000633.GI4657@iris.usta.de> (raw)
In-Reply-To: <D6DE0E56-F8B8-4E8B-BBEE-CD5E7C1CB726@alum.mit.edu>
Hi Guy,
Guy Harris wrote on Tue, Aug 12, 2014 at 03:38:07PM -0700:
> Is there any way to check out a read-only version of the mdocml
> CVS repository using anonymous CVS?
Yes, there is. Not yet for a long time, i only set it up recently
and didn't announce it publicly yet. But Kristaps just agreed
that we can go ahead and tell people about it:
cvs -d anoncvs@mdocml.bsd.lv:/cvs co mdocml
A few caveats about it:
1. Even though the URI given above might give you the impression,
that command does NOT give you access to the master repo, but
to a copy of it, for security reasons.
2. Right now, i'm doing the synching manually. I certainly could
set up a cron job or a commit hook, but i didn't make up my
mind yet. I'm synching fairly often, but may forget now and
then, so it may be out of date by a day or so.
3. While we don't provide any warranties whatsoever for any of
our code but provide it "as is", there is a difference between
HEAD and releases with respect to reliability: Releases tend
to contain old minor bugs that have since been fixed, while
HEAD will occasionally contain new regressions that, in rare
cases, can have considerable impact. So decide carefully what
you want to run in production.
Bug reports are appreciated against both releases and HEAD,
of course.
> I once used some curl hackery to check out the top-of-trunk source,
> but that was a pain,
Uh oh. That does indeed sound painful.
> and I'd like to submit patches against the trunk,
Nice! Thank you in advance, and welcome!
> so that
> 1) you don't get patches to code that's changed since the version
> being patched;
> 2) I can just use "cvs diff" to produce patches;
> 3) if a patch gets checked in, I don't have to keep a copy hanging
> around, and can submit further patches against updated files.
Sure, those are all sound arguments.
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2014-08-13 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 22:38 Guy Harris
2014-08-13 0:06 ` Ingo Schwarze [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=20140813000633.GI4657@iris.usta.de \
--to=schwarze@usta.de \
--cc=discuss@mdocml.bsd.lv \
--cc=guy@alum.mit.edu \
/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 NNTP newsgroup(s).