Package: git-core
Version: 1:1.5.3.8-1
Severity: wishlist

Currently, Git manipulates the working copy in non-atomic ways.  For
instance, when checking out a different branch, Git will unlink files
in the working copy, and later use open and mmap to write them out.
I'd like some way to have Git handle files in the working copy
atomically, such as by writing them out to a temporary file and
atomically renaming them.  In particular, this would make it much
safer to use Git for things like /etc or $HOME.

- Josh Triplett

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.23-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages git-core depends on:
ii  cpio                   2.9-9             GNU cpio -- a program to manage ar
ii  libc6                  2.7-6             GNU C Library: Shared libraries
ii  libcurl3-gnutls        7.17.1-1+b1       Multi-protocol file transfer libra
ii  libdigest-sha1-perl    2.11-2            NIST SHA-1 message digest algorith
ii  liberror-perl          0.17-1            Perl module for error/exception ha
ii  libexpat1              1.95.8-4          XML parsing C library - runtime li
ii  perl-modules           5.8.8-12          Core Perl modules
ii  zlib1g                 1:1.2.3.3.dfsg-11 compression library - runtime

Versions of packages git-core recommends:
ii  curl                         7.17.1-1+b1 Get a file from an HTTP, HTTPS or 
ii  less                         418-1       Pager program similar to more
ii  openssh-client [ssh-client]  1:4.7p1-2   secure shell client, an rlogin/rsh
ii  patch                        2.5.9-4     Apply a diff file to an original
ii  rsync                        2.6.9-6     fast remote file copy program (lik

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to