diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2000-November/000059.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to '')
| -rw-r--r-- | pipermail/nel/2000-November/000059.html | 75 |
1 files changed, 75 insertions, 0 deletions
diff --git a/pipermail/nel/2000-November/000059.html b/pipermail/nel/2000-November/000059.html new file mode 100644 index 00000000..7bc405b0 --- /dev/null +++ b/pipermail/nel/2000-November/000059.html @@ -0,0 +1,75 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] CVS checkin by email</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:archer%40nevrax.com"> + <LINK REL="Previous" HREF="000058.html"> + <LINK REL="Next" HREF="000064.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] CVS checkin by email</H1> + <B>Vincent Archer</B> + <A HREF="mailto:archer%40nevrax.com" + TITLE="[Nel] CVS checkin by email">archer@nevrax.com</A><BR> + <I>Tue, 28 Nov 2000 11:50:58 +0100</I> + <P><UL> + <LI> Previous message: <A HREF="000058.html">[Nel] CVS checkin by email</A></li> + <LI> Next message: <A HREF="000064.html">[Nel] pointers on documentation?</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#59">[ date ]</a> + <a href="thread.html#59">[ thread ]</a> + <a href="subject.html#59">[ subject ]</a> + <a href="author.html#59">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>According to David Mentré: +><i> Hi all, +</I>><i> +</I>><i> Is there any way to bi informed by email of each new CVS checkin ? +</I> +Well, if you want to be spammed continuously, that might be possible. +I'll put something in the crontab to notify you every day :) + +Realistically, since you get full access to the development CVS tree, +there is something done about every day in one part or another of the +library. We do not have anything like the cvsup of FreeBSD so that you +automatically would fetch the latest version everytime, but you can +set a cron job if you like to to a cvs update every day around 23:00 +GMT. That's when we do a full resynchronise of the various CVS mirrors +(in practice, the sync starts at 22:00 GMT, but you never know how long +rsync will take across the 3 machines involved). + +We will post announces when there is something relatively major commited +(like the day you'll get your first pictures, or like we did when the + compilation stuff on Linux boxes started working). Usually, we also do +a manual resync at that time. + +-- +Vincent Archer Email: <A HREF="mailto:archer@nevrax.com">archer@nevrax.com</A> + +Nevrax France. Off on the yellow brick road we go! + +</pre> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000058.html">[Nel] CVS checkin by email</A></li> + <LI> Next message: <A HREF="000064.html">[Nel] pointers on documentation?</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#59">[ date ]</a> + <a href="thread.html#59">[ thread ]</a> + <a href="subject.html#59">[ subject ]</a> + <a href="author.html#59">[ author ]</a> + </LI> + </UL> +</body></html> |