From: Bron Gondwana <brong@fastmail.fm>
To: "J.H." <warthog19@eaglescrag.net>
Cc: Bron Gondwana <brong@fastmail.fm>, git@vger.kernel.org, pape@smarden.org
Subject: Re: Why /var/cache/git?
Date: Tue, 26 Oct 2010 12:22:24 +1100 [thread overview]
Message-ID: <20101026012224.GA3360@brong.net> (raw)
In-Reply-To: <4CC5A13F.2090702@eaglescrag.net>
On Mon, Oct 25, 2010 at 08:24:47AM -0700, J.H. wrote:
> On 10/25/2010 03:30 AM, Bron Gondwana wrote:
> > (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...)
>
> Couple of quick points:
>
> $ grep -Ri "/var/git\|\/var\/git" *
> Documentation/git-cvsserver.txt: export
> CVSROOT=:ext:user@server:/var/git/project.git
>
> gitweb/README: RewriteRule ^/var(/|/gitweb.cgi)?$
> /cgi-bin/gitweb.cgi [QSA,E=GITWEB_PROJECTROOT:/var/git/,L,PT]
>
> gitweb/README:Second, repositories found in /pub/scm/ and /var/git/ will
> be accesible
>
> Are the only 3 instances where this is mentioned. Looking at those
> quick it was probably chosen based on the fact that it's a location that
> likely exists on most machines. Or just for explanatory reasons like
> /example/dir/project.git could be used.
I have no problem with /var/git - it's /var/cache/git that worries
me, since the FHS quite clearly says that blowing away /var/cache/*
is not a problem. It makes sense to back up /var/lib/ on any machine,
since that's somewhere that contains application data. We already
back up a few things from /var/lib (like /var/lib/svn for example,
at least until we finish this switchover!)
Bron.
next prev parent reply other threads:[~2010-10-26 1:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 10:30 Why /var/cache/git? Bron Gondwana
2010-10-25 15:24 ` J.H.
2010-10-26 1:22 ` Bron Gondwana [this message]
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=20101026012224.GA3360@brong.net \
--to=brong@fastmail.fm \
--cc=git@vger.kernel.org \
--cc=pape@smarden.org \
--cc=warthog19@eaglescrag.net \
/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.