Git development
 help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 09/11] Provide API access to init_db()
Date: Sat, 8 Mar 2008 18:55:29 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.1.00.0803081840070.19665@iabervon.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0803090026170.3975@racer.site>

On Sun, 9 Mar 2008, Johannes Schindelin wrote:

> On Sat, 8 Mar 2008, Daniel Barkalow wrote:
> 
> > The caller first calls set_git_dir() to specify the GIT_DIR, and then 
> > calls init_db() to initialize it. This also cleans up various parts of 
> > the code to account for the fact that everything is done with GIT_DIR 
> > set, so it's unnecessary to pass the specified directory around.
> 
> I think the most controversial part is that you change the way it is 
> determined if the repository is a bare one.  It might have the same 
> result (I do not have time to check it...), but the computation is 
> performed differently.

It's actually doing the same computation; the difference is how the result 
is reported. Mine commits to the repo being non-bare if it doesn't think 
it's bare, which the current code leaves as "we don't know, assume 
non-bare". But since we actually create a work tree if we guess it's 
non-bare, it really is non-bare. So then the later code can assume it's 
either 0 or 1, and not worry about -1 being equivalent to 0.

	-Daniel
*This .sig left intentionally blank*

  reply	other threads:[~2008-03-08 23:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-08 23:04 [PATCH 09/11] Provide API access to init_db() Daniel Barkalow
2008-03-08 23:27 ` Johannes Schindelin
2008-03-08 23:55   ` Daniel Barkalow [this message]
2008-03-09 20:43     ` Johannes Schindelin

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.LNX.1.00.0803081840070.19665@iabervon.org \
    --to=barkalow@iabervon.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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