<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include/asm-alpha/errno.h, branch v2.6.19</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/include/asm-alpha/errno.h?h=v2.6.19</id>
<link rel='self' href='https://git.amat.us/linux/atom/include/asm-alpha/errno.h?h=v2.6.19'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2005-05-01T15:59:06Z</updated>
<entry>
<title>[PATCH] add EOWNERDEAD and ENOTRECOVERABLE version 2</title>
<updated>2005-05-01T15:59:06Z</updated>
<author>
<name>Joe Korty</name>
<email>joe.korty@ccur.com</email>
</author>
<published>2005-05-01T15:59:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4750e2c0c59e0c84c6c036b3d96ebd88365ae7ee'/>
<id>urn:sha1:4750e2c0c59e0c84c6c036b3d96ebd88365ae7ee</id>
<content type='text'>
Add EOWNERDEAD and ENOTRECOVERABLE to all architectures.  This is to
support the upcoming patches for robust mutexes.

We normally don't reserve parts of the name/number space for external
patches, but robust mutexes are sufficiently popular and important to
justify it in this case.

Signed-off-by: Joe Korty &lt;joe.korty@ccur.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>Linux-2.6.12-rc2</title>
<updated>2005-04-16T22:20:36Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@ppc970.osdl.org</email>
</author>
<published>2005-04-16T22:20:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2'/>
<id>urn:sha1:1da177e4c3f41524e886b7f1b8a0c1fc7321cac2</id>
<content type='text'>
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!
</content>
</entry>
</feed>
