#
77501f3c |
| 18-Oct-2005 |
Jeff Garzik <jgarzik@pobox.com> |
Merge branch 'upstream'
|
#
cff6bf97 |
| 18-Oct-2005 |
Trond Myklebust <Trond.Myklebust@netapp.com> |
Merge /home/trondmy/scm/kernel/git/torvalds/linux-2.6
|
#
59aee3c2 |
| 13-Oct-2005 |
Jeff Garzik <jgarzik@pobox.com> |
Merge branch 'master'
|
#
7217cbcc |
| 13-Oct-2005 |
Trond Myklebust <Trond.Myklebust@netapp.com> |
Merge rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
|
#
b6ec995a |
| 11-Oct-2005 |
Paul Mackerras <paulus@samba.org> |
Merge from Linus' tree
|
#
29d8699e |
| 11-Oct-2005 |
Anton Altaparmakov <aia21@cantab.net> |
Merge branch 'master' of /usr/src/ntfs-2.6/
|
#
1a04392b |
| 11-Oct-2005 |
Jeff Garzik <jgarzik@pobox.com> |
Merge branch 'master'
|
Revision tags: v2.6.14-rc4 |
|
#
dd0fc66f |
| 07-Oct-2005 |
Al Viro <viro@ftp.linux.org.uk> |
[PATCH] gfp flags annotations - part 1
- added typedef unsigned int __nocast gfp_t;
- replaced __nocast uses for gfp flags with gfp_t - it gives exactly the same warnings as far as sparse is c
[PATCH] gfp flags annotations - part 1
- added typedef unsigned int __nocast gfp_t;
- replaced __nocast uses for gfp flags with gfp_t - it gives exactly the same warnings as far as sparse is concerned, doesn't change generated code (from gcc point of view we replaced unsigned int with typedef) and documents what's going on far better.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
show more ...
|
Revision tags: v2.6.14-rc3, v2.6.14-rc2, v2.6.14-rc1, v2.6.13, v2.6.13-rc7, v2.6.13-rc6, v2.6.13-rc5, v2.6.13-rc4, v2.6.13-rc3, v2.6.13-rc2, v2.6.13-rc1, v2.6.12, v2.6.12-rc6, v2.6.12-rc5, v2.6.12-rc4, v2.6.12-rc3, v2.6.12-rc2 |
|
#
1da177e4 |
| 16-Apr-2005 |
Linus Torvalds <torvalds@ppc970.osdl.org> |
Linux-2.6.12-rc2
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
Linux-2.6.12-rc2
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!
show more ...
|