git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: David Aguilar <davvid@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitk: do not show local changes for bare repositories
Date: Fri, 7 Mar 2008 10:07:33 +1100	[thread overview]
Message-ID: <18384.31029.243013.764703@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <64b42ab91804e670057c807fd8265fc07106792c.1204806475.git.davvid@gmail.com>

David Aguilar writes:

> +set isbare [expr {[exec git rev-parse --is-bare-repository] == "true"}]

Nice idea, but I think we should update isbare in updatecommits, in
case the user does a checkout and then presses F5.

Paul.

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 12:39 [PATCH] gitk: do not show local changes for bare repositories David Aguilar
2008-03-06 23:07 ` Paul Mackerras [this message]
2008-03-07  9:04 ` David Aguilar
2008-03-08 11:14   ` Paul Mackerras
2008-03-10 10:54     ` [PATCH] gitk: do not show local changes when we there is no work tree David Aguilar

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=18384.31029.243013.764703@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    /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).