Linus Torvalds reply about Meltdown and Spectre. Post: 303012275

5 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

What the best HD format for Unix & Linus

Hello people, Im just about to install linux and unix but would like to know what the best Partition type format is for both of them. Can anyone tell me Thankyou in advanced

2. Filesystems, Disks and Memory

hard disk meltdown

I had an issue with a second hard disk in my machine. I have a sparc station running solaris 7. It was working fine but now it wont mount on boot up and when you try to mount it manually it gives an I/O error. I tried a different disk as a control which was fine. What I want to know is if my...

3. News, Links, Events and Announcements

A Couple of Short Linus Torvalds Videos

This link is to a page that has two short videos that feature Linus Torvalds discussing the Linux kernel. After you watch the first video, scroll down some more to reach the second video.

4. What is on Your Mind?

Meltdown and Spectre CPU bugs

This seems a bit serious: Meltdown, Spectre: The password theft bugs at the heart of Intel CPUs � The Register Vulnerability Note VU#584653 - CPU hardware vulnerable to side-channel attacks Project Zero: Reading privileged memory with a side-channel

5. AIX

AIX 6.1, POWER5 and Spectre/Meltdown

Apologies for this newbie question. We have inherited an IBM p5 520 (9111-520) running AIX 6.1.0.0 which seems to be the base install and no further patches installed. Is this vulnerable to the Spectre/Meltdown threat? Are patches available? Looks like AIX 6.1.0.0 went 'end of support' in...

LEARN ABOUT SUSE

git-prune

GIT-PRUNE(1)							    Git Manual							      GIT-PRUNE(1)

NAME

       git-prune - Prune all unreachable objects from the object database

SYNOPSIS

       git prune [-n] [-v] [--expire <expire>] [--] [<head>...]

DESCRIPTION

	   Note
	   In most cases, users should run git gc, which calls git prune. See the section "NOTES", below.

       This runs git fsck --unreachable using all the refs available in refs/, optionally with additional set of objects specified on the command
       line, and prunes all unpacked objects unreachable from any of these head objects from the object database. In addition, it prunes the
       unpacked objects that are also found in packs by running git prune-packed.

       Note that unreachable, packed objects will remain. If this is not desired, see git-repack(1).

OPTIONS

       -n
	   Do not remove anything; just report what it would remove.

       -v
	   Report all removed objects.

       --
	   Do not interpret any more arguments as options.

       --expire <time>
	   Only expire loose objects older than <time>.

       <head>...
	   In addition to objects reachable from any of our references, keep objects reachable from listed <head>s.

EXAMPLE

       To prune objects not used by your repository nor another that borrows from your repository via its .git/objects/info/alternates:

	   .ft C
	   $ git prune $(cd ../another && $(git rev-parse --all))
	   .ft

NOTES

       In most cases, users will not need to call git prune directly, but should instead call git gc, which handles pruning along with many other
       housekeeping tasks.

       For a description of which objects are considered for pruning, see git fsck's --unreachable option.

SEE ALSO

       git-fsck(1), git-gc(1), git-reflog(1)

AUTHOR

       Written by Linus Torvalds <torvalds@osdl.org[1]>

DOCUMENTATION

       Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org[2]>.

GIT

       Part of the git(1) suite

NOTES

	1. torvalds@osdl.org
	   mailto:torvalds@osdl.org

	2. git@vger.kernel.org
	   mailto:git@vger.kernel.org

Git 1.7.1							    07/05/2010							      GIT-PRUNE(1)