From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Thomas Rast <trast@student.ethz.ch>,
Robin Rosenberg <robin.rosenberg@dewire.com>,
git@vger.kernel.org, sasa.zivkov@sap.com
Subject: Re: [PATCH] Don't create the $GIT_DIR/branches directory on init
Date: Sat, 31 Oct 2009 11:24:16 -0700 [thread overview]
Message-ID: <20091031182416.GO10505@spearce.org> (raw)
In-Reply-To: <7vr5sj8m5f.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
> Modern git Porcelains write remote definitions solely to .git/config, but
> still reads from .git/{branches,remotes}.
...
> Andrew Morton explicitly asked for this to be kept a few years
> ago and I do not see a reason to deprecate this.
...
> Shawn and other wants to stop JGit from creating this directory on
I probably said something like this. I won't bother denying it,
because list archives are more accurate than my own fallible memory.
But I didn't know the Andrew Morton part above. After hearing it
from you, I'm reversing my (apparent) direction here. We should
continue to create the branches directory within a new repository.
Sorry Robin, but Andrew Morton matters. Its one stupid unused
directory in a repository that will chew through thousands of inodes
as loose objects. Its a drop in the bucket in terms of resource
cost used by Git. And Andrew is someone whose workflow we don't
want to break if we can avoid it. He's a long time Git user who is
also high up in the kernel food chain. Interrupting him disrupts
a fair chunk of kernel work while he grumbles about the Goddamn
Idiotic Truckload of s**t that Linus begat.
> This patch alone breaks tests in the t55?? series quite a lot,
Drop the patch.
--
Shawn.
next prev parent reply other threads:[~2009-10-31 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 17:20 [PATCH] Don't create the $GIT_DIR/branches directory on init Robin Rosenberg
2009-10-30 21:35 ` Junio C Hamano
2009-10-31 9:11 ` Thomas Rast
2009-10-31 18:02 ` Robin Rosenberg
2009-10-31 18:09 ` Shawn O. Pearce
2009-10-31 18:15 ` Junio C Hamano
2009-10-31 18:24 ` Shawn O. Pearce [this message]
2009-10-31 19:32 ` Junio C Hamano
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=20091031182416.GO10505@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robin.rosenberg@dewire.com \
--cc=sasa.zivkov@sap.com \
--cc=trast@student.ethz.ch \
/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.