From: David Aguilar <davvid@gmail.com>
To: Sam Vilain <sam@vilain.net>
Cc: paulus@samba.org, git@vger.kernel.org
Subject: Re: [PATCH] gitk: Add ability to define an alternate temporary directory
Date: Tue, 10 Nov 2009 20:07:16 -0800 [thread overview]
Message-ID: <20091111040715.GA44672@gmail.com> (raw)
In-Reply-To: <4AFA368F.207@vilain.net>
On Wed, Nov 11, 2009 at 04:59:11PM +1300, Sam Vilain wrote:
> David Aguilar wrote:
> > gitk fails to show diffs when browsing a repository for which
> > we have read-only access. This is due to gitk's assumption
> > that the current directory is always writable.
> >
> > This teaches gitk to honor the GITK_TMPDIR environment
> > variable. This allows users to override the default location
> > used for writing temporary files.
> >
>
> Is there a good reason not to use the common TMPDIR or TMP environment
> variables for this?
I, personally, would not be opposed to that.
The only reason I chose a different variable was that I didn't
want to change the existing behavior (backwards-compat hat on).
Since TMPDIR and TMP are common then we'd be changing the
behavior.
That said, if there's a consensus that the path doesn't matter
much than we could change the behavior. I was just trying to be
careful.
--
David
next prev parent reply other threads:[~2009-11-11 4:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 1:49 [PATCH] gitk: Add ability to define an alternate temporary directory David Aguilar
2009-11-11 1:49 ` [PATCH] gitk: Document the $GITK_TMPDIR variable David Aguilar
2009-11-11 3:59 ` [PATCH] gitk: Add ability to define an alternate temporary directory Sam Vilain
2009-11-11 4:07 ` David Aguilar [this message]
2009-11-11 4:42 ` Junio C Hamano
2009-11-11 16:44 ` David Aguilar
2009-11-12 8:35 ` Jeff King
2009-11-12 9:36 ` David Aguilar
2009-11-12 9:56 ` 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=20091111040715.GA44672@gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sam@vilain.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.