<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test2/lib/libutil/login_crypt.c, branch master</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test2/atom?h=master</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test2/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/'/>
<updated>2017-11-26T02:00:33Z</updated>
<entry>
<title>lib: further adoption of SPDX licensing ID tags.</title>
<updated>2017-11-26T02:00:33Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2017-11-26T02:00:33Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=5e53a4f90f82c4345f277dd87cc9292f26e04a29'/>
<id>urn:sha1:5e53a4f90f82c4345f277dd87cc9292f26e04a29</id>
<content type='text'>
Mainly focus on files that use BSD 2-Clause license, however the tool I
was using mis-identified many licenses so this was mostly a manual - error
prone - task.

The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.
</content>
</entry>
<entry>
<title>Const poisoning.</title>
<updated>2002-04-08T11:04:56Z</updated>
<author>
<name>Ruslan Ermilov</name>
<email>ru@FreeBSD.org</email>
</author>
<published>2002-04-08T11:04:56Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=b00ba4ccbbc47007464062814d062702e3123276'/>
<id>urn:sha1:b00ba4ccbbc47007464062814d062702e3123276</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add __FBSDID()s to libutil</title>
<updated>2001-09-30T22:35:07Z</updated>
<author>
<name>Matthew Dillon</name>
<email>dillon@FreeBSD.org</email>
</author>
<published>2001-09-30T22:35:07Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=8719c58fefefd5ceebb076be7e40b2a2be317c36'/>
<id>urn:sha1:8719c58fefefd5ceebb076be7e40b2a2be317c36</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix problems people were having with large -O levels with GCC and</title>
<updated>2000-10-27T01:19:02Z</updated>
<author>
<name>Brian Feldman</name>
<email>green@FreeBSD.org</email>
</author>
<published>2000-10-27T01:19:02Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=aa8645587548066172f5222d842444f198ec5613'/>
<id>urn:sha1:aa8645587548066172f5222d842444f198ec5613</id>
<content type='text'>
getting libutil/libcrypt to work properly.  I've determined that GCC
thinks it can inline all functions, including weak-symboled ones, if
it feels like it.

Create a new stub.c and move any stubs there to prevent inlining.
Thanks to jdp and William S. Duncanson for helping me finally find the
problem.
</content>
</entry>
<entry>
<title>Add weak symbol pragma for crypt_set_format().</title>
<updated>2000-08-23T11:54:10Z</updated>
<author>
<name>Jeroen Ruigrok van der Werven</name>
<email>asmodai@FreeBSD.org</email>
</author>
<published>2000-08-23T11:54:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=de4b2114a43e503e34fbcff350b9ad39c892d035'/>
<id>urn:sha1:de4b2114a43e503e34fbcff350b9ad39c892d035</id>
<content type='text'>
Approved by:	green
</content>
</entry>
<entry>
<title>Stick login_setcryptfmt() in its own file to make pulling in of</title>
<updated>2000-08-23T03:45:57Z</updated>
<author>
<name>Brian Feldman</name>
<email>green@FreeBSD.org</email>
</author>
<published>2000-08-23T03:45:57Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=c2534fa193116b8c41d3f7c91c49a9bea6c73fc8'/>
<id>urn:sha1:c2534fa193116b8c41d3f7c91c49a9bea6c73fc8</id>
<content type='text'>
-lcrypt only happen if truly necessary.
</content>
</entry>
</feed>
