Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Oct 28, 2005
  1. Be marginally more careful about removing objects

    Linus Torvalds authored Junio C Hamano committed
    The git philosophy when it comes to disk accesses is "Laugh in the face of
    Notably, since we never modify an existing object, we don't really care
    that deeply about flushing things to disk, since even if the machine
    crashes in the middle of a git operation, you can never really have lost
    any old work. At most, you'd need to figure out the proper heads (which
    git-fsck-objects can do for you) and re-do the operation.
    However, there's two exceptions to this: pruning and repacking. Those
    operations will actually _delete_ old objects that they know about in
    other ways (ie that they just repacked, or that they have found in other
    However, since they actually modify old state, we should thus be a bit
    more careful about them. If the machine crashes and the duplicate new
    objects haven't been flushed to disk, you can actually be in trouble.
    This is trivially stupid about it by calling "sync" before removing the
    objects. Not very smart, but we're talking about special operations than
    are usually done once a week if that.
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Junio C Hamano <>
Commits on Oct 13, 2005
  1. Add "-l" flag for repacking only local packs

    Linus Torvalds authored Junio C Hamano committed
    This uses the new "--local" flag to git-pack-objects.  It currently only
    makes a difference together with "-a", since a normal incremental repack
    won't pack any packed objects at all (whether local or remote).
    Eventually, it might end up skipping any objects that aren't local to
    the current object directory, but for now it only knows to skip packed
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Junio C Hamano <>
Commits on Sep 18, 2005
  1. Archive-destroying "git repack -a -d" bug.

    Junio C Hamano authored
    Using "git repack -a -d" can destroy your git archive if you use it
    twice in succession, because the new pack can be called the same as
    the old pack.  Found by Linus.
    Signed-off-by: Junio C Hamano <>
Commits on Sep 8, 2005
  1. Big tool rename.

    Junio C Hamano authored
    As promised, this is the "big tool rename" patch.  The primary differences
    since 0.99.6 are:
      (1) git-*-script are no more.  The commands installed do not
          have any such suffix so users do not have to remember if
          something is implemented as a shell script or not.
      (2) Many command names with 'cache' in them are renamed with
          'index' if that is what they mean.
    There are backward compatibility symblic links so that you and
    Porcelains can keep using the old names, but the backward
    compatibility support  is expected to be removed in the near
    Signed-off-by: Junio C Hamano <>
Something went wrong with that request. Please try again.