git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bill lam <cbill.lam@gmail.com>
To: Jonas Fonseca <jonas.fonseca@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: tool and worktree
Date: Mon, 9 Feb 2009 10:15:08 +0800	[thread overview]
Message-ID: <20090209021508.GA7599@b2j> (raw)
In-Reply-To: <2c6b72b30902081717q35fd4ba0k6ff5b1be8cd5ef2c@mail.gmail.com>

On Mon, 09 Feb 2009, Jonas Fonseca wrote:
> On Sun, Feb 8, 2009 at 10:47, Jonas Fonseca <jonas.fonseca@gmail.com> wrote:
> > It might be as
> > simple as setting the GIT_DIR environment to getcwd() + output of
> > git-rev-parse --git-dir and then chdir() to core.worktree.
> 
> I have pushed a lightly tested patch that does something like this ...

Thanks. Now the status view works.

Since /etc contains both public and private files.  When browsing the
untracked files in the status view, for files that without read
permission, eg the shadow passwd file, the lower pane displays the
content of the last readable file.  Could it clear the content or just
filter and display only files with read permission for the untracked
files?

-- 
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩215 李商隱  無題
    相見時難別亦難  東風無力百花殘  春蠶到死絲方盡  蠟炬成灰淚始乾
    曉鏡但愁雲鬢改  夜吟應覺月光寒  蓬萊此去無多路  青鳥殷勤為探看

  reply	other threads:[~2009-02-09  2:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08  3:44 tool and worktree bill lam
2009-02-08  9:47 ` Jonas Fonseca
2009-02-09  1:17   ` Jonas Fonseca
2009-02-09  2:15     ` bill lam [this message]
2009-02-09  3:23       ` Jonas Fonseca
2009-02-08 19:25 ` Shawn O. Pearce
  -- strict thread matches above, loose matches on Subject: below --
2009-02-09 16:19 [RFC/RFH] Fun things with git-notes, or: patch tracking backwards SZEDER Gábor
2009-02-09 17:49 ` tool and worktree Giuseppe Bilotta

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=20090209021508.GA7599@b2j \
    --to=cbill.lam@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jonas.fonseca@gmail.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;
as well as URLs for NNTP newsgroup(s).