git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Kristian Høgsberg" <krh@bitplanet.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Remove .git/branches from the .git template.
Date: Sun, 09 Dec 2007 10:30:55 -0800	[thread overview]
Message-ID: <7v3aubpvog.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071209183856.GA5587@bitplanet.net> (Kristian Høgsberg's message of "Sun, 9 Dec 2007 13:38:56 -0500")

Kristian Høgsberg <krh@bitplanet.net> writes:

> The code in git to read the info in .git/branches is still there,
> but nothing ever writes to this, so lets stop creating it.
>
> Signed-off-by: Kristian Høgsberg <krh@redhat.com>
> ---
>
> As far as I can see this should be safe, but I admit to never really
> knowing what .git/branches was originally used for - tracking remote
> branches or something?  In any case, we only ever read from this dir
> so the only left in git to deal with this seems to be for compatibilty
> with older repos.

This was done purely so that Cogito would not barf on a repository
initialized with "git init" even if it did not bother creating necessary
leading directories when it writes its rough equivalent to .git/remotes/
information.  I do not recall if Cogito had such a problem anymore, but
I think it can safely go when Cogito is effectively dead.

  reply	other threads:[~2007-12-09 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-09 18:38 [PATCH] Remove .git/branches from the .git template Kristian Høgsberg
2007-12-09 18:30 ` Junio C Hamano [this message]
2007-12-10  4:34   ` Kristian Høgsberg

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=7v3aubpvog.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=krh@bitplanet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).