Page MenuHomeFreeBSD

exit(3) man page: Add HISTORY section
ClosedPublic

Authored by carlavilla on Mar 22 2020, 11:31 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Nov 20, 9:09 PM
Unknown Object (File)
Sun, Nov 10, 5:44 PM
Unknown Object (File)
Sat, Nov 2, 11:32 AM
Unknown Object (File)
Fri, Nov 1, 1:46 AM
Unknown Object (File)
Oct 8 2024, 4:17 PM
Unknown Object (File)
Oct 8 2024, 4:16 PM
Unknown Object (File)
Oct 8 2024, 4:16 PM
Unknown Object (File)
Oct 8 2024, 3:56 PM
Subscribers

Details

Summary

exit(3) man page: Add HISTORY section

MFC: 2 days

PR: 240259

Test Plan

Compile the manpage

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Also ready for commit, thanks!

This revision is now accepted and ready to land.Mar 22 2020, 11:53 AM

I'd add a source of this data to the commit message, since we have the tuhs archive.
And it was also present in pdp7 unix, but there is no good way to call that out.

@imp I can't find the source code of the 1.0 release. The oldest version I found is release 2.0
That's what you want to have in the commit message?

Thanks for your help.

FreeBSD 1.x is a bit hard to fund due to AT&T lawsuits.
https://github.com/dspinellis/unix-history-repo
is a good source for historical releases, though it only has FreeBSD 1.0, not 1.1 nor 1.1.5

Wow ... well, it's a problem. I had read about FreeBSD's problems with the AT&T lawsuits. But do not think that for these problems the source code of version 1.0 did not exist as such.

So...

What could I put in the commit @imp ? Could you give me an example?

Wow ... well, it's a problem. I had read about FreeBSD's problems with the AT&T lawsuits. But do not think that for these problems the source code of version 1.0 did not exist as such.

So...

What could I put in the commit @imp ? Could you give me an example?

I'd look at any of my commit messages for history additions.

Some examples of what you can use for your work:

Obtained from: OpenBSD (verified with TUHS)

or

Consulting TUHS shows this was in the first edition.

or something similar. This allows others to verify too.

This revision was automatically updated to reflect the committed changes.