Hello, Christian Baer wrote:This was discussed many times in -stable mail list (and probably on few others?) Anyway STABLE means stable API, so programs compiled on 6.2-RELEASE should work on 6.2-STABLE You can look for "ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!" - very long thread, but normally when something broke in -stable this thread start and start again. P.S. for me STABLE is very stable, and current CURRENT is even more stable (at least on new hardware), and I have both in production. -- Best Wishes, Stefan Lambrev ICQ# 24134177 _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Linux 2.6.25-rc4 |
| Greg KH | Linux 2.6.25.10 |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Ilpo Järvinen | Re: Strange Application bug, race in MSG_PEEK complaints (was: Bug#513695: fetchma... |
