PageRenderTime 50ms CodeModel.GetById 22ms RepoModel.GetById 0ms app.codeStats 0ms

/old-site/archive/2007-April/001227.html

http://github.com/bjdean/cambridge-pm-website
HTML | 79 lines | 66 code | 10 blank | 3 comment | 0 complexity | ca1f97b36c1ca3403b1572a22ddcb860 MD5 | raw file
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
  2. <HTML>
  3. <HEAD>
  4. <TITLE> [cam.pm] Backups + next pubmeet, Re: Hangover over?
  5. </TITLE>
  6. <LINK REL="Index" HREF="index.html" >
  7. <LINK REL="made" HREF="mailto:cam.pm%40cam.pm.org?Subject=%5Bcam.pm%5D%20Backups%20%2B%20next%20pubmeet%2C%20Re%3A%20Hangover%20over%3F&In-Reply-To=20070421132115.GK18070%40t8o.org">
  8. <META NAME="robots" CONTENT="index,nofollow">
  9. <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10. <LINK REL="Previous" HREF="001226.html">
  11. <LINK REL="Next" HREF="001230.html">
  12. </HEAD>
  13. <BODY BGCOLOR="#ffffff">
  14. <H1>[cam.pm] Backups + next pubmeet, Re: Hangover over?</H1>
  15. <B>Robbie Bow</B>
  16. <A HREF="mailto:cam.pm%40cam.pm.org?Subject=%5Bcam.pm%5D%20Backups%20%2B%20next%20pubmeet%2C%20Re%3A%20Hangover%20over%3F&In-Reply-To=20070421132115.GK18070%40t8o.org"
  17. TITLE="[cam.pm] Backups + next pubmeet, Re: Hangover over?">robbie at robbiebow.co.uk
  18. </A><BR>
  19. <I>Sun Apr 22 09:11:37 BST 2007</I>
  20. <P><UL>
  21. <LI>Previous message: <A HREF="001226.html">[cam.pm] Backups + next pubmeet, Re: Hangover over?
  22. </A></li>
  23. <LI>Next message: <A HREF="001230.html">[cam.pm] Hangover over?
  24. </A></li>
  25. <LI> <B>Messages sorted by:</B>
  26. <a href="date.html#1227">[ date ]</a>
  27. <a href="thread.html#1227">[ thread ]</a>
  28. <a href="subject.html#1227">[ subject ]</a>
  29. <a href="author.html#1227">[ author ]</a>
  30. </LI>
  31. </UL>
  32. <HR>
  33. <!--beginarticle-->
  34. <PRE> &gt; I would prefer a non-Wednesday day. No doubt everyone has different
  35. &gt; days to avoid. 8-}
  36. Always a devil to get this sort of thing right. Fridays are normally a
  37. Bad Idea; Thursdays sometimes also for some people. Maybe rotate the day
  38. of the week each month (Monday-Friday) so the 3rd Thursday of the month
  39. next month, 3rd Friday of June &amp;c. That would please all of the people
  40. all of the time...
  41. &gt; Do people really want closed software copying their data back to some
  42. &gt; random company? It doesn't seem like the best idea.
  43. It's not ideal, but it's infinitely better than what 99% of normal users
  44. have, e.g. no backup regime at all. If I never have to explain to
  45. someone that they lost all their emails because of a hard disk failure /
  46. that they should use IMAP / have backups it'll be a good thing.
  47. Looks like there's a gap that needs filling: open automated offsite
  48. backups. I'll add that to my
  49. things-that-would-be-great-to-do-but-I-never-will list.
  50. </PRE>
  51. <!--endarticle-->
  52. <HR>
  53. <P><UL>
  54. <!--threads-->
  55. <LI>Previous message: <A HREF="001226.html">[cam.pm] Backups + next pubmeet, Re: Hangover over?
  56. </A></li>
  57. <LI>Next message: <A HREF="001230.html">[cam.pm] Hangover over?
  58. </A></li>
  59. <LI> <B>Messages sorted by:</B>
  60. <a href="date.html#1227">[ date ]</a>
  61. <a href="thread.html#1227">[ thread ]</a>
  62. <a href="subject.html#1227">[ subject ]</a>
  63. <a href="author.html#1227">[ author ]</a>
  64. </LI>
  65. </UL>
  66. <hr>
  67. <a href="http://cam.pm.org/list/listinfo/cam.pm">More information about the Cam.pm
  68. mailing list</a><br>
  69. </body></html>