NetBSD

Commit Graph

Author	SHA1	Message	Date
rumble	3691c21c61	Minor english nits.	2006-09-06 14:59:15 +00:00
jmmv	d2cb59a6d2	Add a "how to report bugs" message for STABLE branches too, as they really are development snapshots (although not as "bleeding edge" as current). Per tron@'s suggestion. This way we get consistent messages along the development process. Otherwise, STABLE could carry no message while a RC could, disappearing again after the real formal release. With this change only formal releases do not carry any special message in motd.	2006-08-13 14:11:36 +00:00

Author

SHA1

Message

Date

rumble

3691c21c61

Minor english nits.

2006-09-06 14:59:15 +00:00

jmmv

d2cb59a6d2

Add a "how to report bugs" message for STABLE branches too, as they really

are development snapshots (although not as "bleeding edge" as current).
Per tron@'s suggestion.

This way we get consistent messages along the development process.  Otherwise,
STABLE could carry no message while a RC could, disappearing again after the
real formal release.  With this change only formal releases do not carry any
special message in motd.

2006-08-13 14:11:36 +00:00

2 Commits