All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bron Gondwana <brong@fastmail.fm>
To: git@vger.kernel.org
Cc: pape@smarden.org
Subject: Why /var/cache/git?
Date: Mon, 25 Oct 2010 21:30:06 +1100	[thread overview]
Message-ID: <20101025103006.GA18782@brong.net> (raw)

(resent - correct address for git list!)

(Gerrit: you're CC'd as the attribution in README.Debian
 which in the one place I can see /var/cache/git mentioned
 in the docs - without a justification for why it was
 chosen...)

I'm setting up shared repositories on a machine, and I notice
all the examples I can find on the web, and also the 
auto-created directory from the packages are /var/cache/git/

So I looked at the FHS, because that seemed odd to me:

http://www.pathname.com/fhs/pub/fhs-2.3.html#VARCACHEAPPLICATIONCACHEDATA

    /var/cache is intended for cached data from applications.
    Such data is locally generated as a result of time-consuming
    I/O or calculation. The application must be able to regenerate
    or restore the data. Unlike /var/spool, the cached files can
    be deleted without data loss.

I guess in theory, someone else has all those commits in their
local git repository somewhere.  Still, it feels to me that
/var/lib/git is the correct location.  Is there any reason why
/var/spool/git was chosen?

(I'm running Debian Lenny with the 1.7.1 backport packages, but
I see examples from Fedora with the same paths as well)

Bron.

             reply	other threads:[~2010-10-25 10:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25 10:30 Bron Gondwana [this message]
2010-10-25 15:24 ` Why /var/cache/git? J.H.
2010-10-26  1:22   ` Bron Gondwana
2010-10-26 13:21     ` Drew Northup
2010-10-26 15:22       ` Gerrit Pape
2010-10-26 16:47         ` Jakub Narebski
2010-10-26 18:30         ` Junio C Hamano
2010-10-28 15:53           ` Gerrit Pape
2010-10-26 20:58         ` Bron Gondwana

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101025103006.GA18782@brong.net \
    --to=brong@fastmail.fm \
    --cc=git@vger.kernel.org \
    --cc=pape@smarden.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.