Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, Kevin Ballard <kevin@sb.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: To page or not to page
Date: Fri, 16 May 2008 11:29:17 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0805161129010.30431@racer> (raw)
In-Reply-To: <20080516045139.GA10858@sigill.intra.peff.net>

Hi,

On Fri, 16 May 2008, Jeff King wrote:

> On Fri, May 16, 2008 at 12:42:38AM -0400, Jeff King wrote:
> 
> > So the logic in setup_git_env seems bogus, but should basically never 
> > be invoked because we do generally call setup_git_directory_gently 
> > before then. Either it should probably call setup_git_directory_gently 
> > (though I am afraid of what awful side effects that could have), or it 
> > should just barf, and people should do setup_git_directory beforehand 
> > (and I'm sure that will break something too).
> 
> Hrm. So there are lots of programs that actually _do_ end up needing 
> this lazy load of the git_dir, but it's just that we have 
> setup_git_directory'd ourselves into the top of the work tree by then.
> 
> So it would be nice if we could move that earlier so that the wrapper 
> could do useful things like look at the proper config. But I think that 
> opens a whole can of worms with running setup_git_directory twice, IIRC.

Yes.  There be dragons.

Ciao,
Dscho

  reply	other threads:[~2008-05-16 10:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02  5:41 To page or not to page Kevin Ballard
2008-05-02  5:45 ` Jeff King
2008-05-02  5:56   ` Junio C Hamano
2008-05-02  6:04     ` Kevin Ballard
2008-05-02  6:08       ` Junio C Hamano
2008-05-02 13:47         ` Bart Trojanowski
2008-05-02  9:41       ` Pedro Melo
2008-05-02 16:58         ` Kevin Ballard
2008-05-02 10:34       ` Wincent Colaiuta
2008-05-02 12:36         ` Jeff King
2008-05-02 13:49           ` Pedro Melo
2008-05-02 14:00           ` Aidan Van Dyk
2008-05-02 16:13           ` Wincent Colaiuta
2008-05-02 16:56             ` Kevin Ballard
2008-05-02 18:40               ` Wincent Colaiuta
2008-05-02  6:11     ` Jeff King
2008-05-02  7:53       ` Johannes Schindelin
2008-05-02  6:09   ` Jeff King
2008-05-02  6:19     ` Junio C Hamano
2008-05-02 12:55       ` Jeff King
2008-05-02 18:18         ` Junio C Hamano
2008-05-05 21:59           ` Jeff King
2008-05-06  5:51           ` Jeff King
2008-05-06  5:53             ` Jeff King
2008-05-11 17:15             ` Junio C Hamano
2008-05-16  4:42             ` Jeff King
2008-05-16  4:51               ` Jeff King
2008-05-16 10:29                 ` Johannes Schindelin [this message]
2008-05-02  6:56     ` Jakub Narebski
2008-05-02 12:57       ` Jeff King
2008-05-02 15:36     ` Jeff King

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=alpine.DEB.1.00.0805161129010.30431@racer \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kevin@sb.org \
    --cc=peff@peff.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