All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Eitzenberger <holger@my-eitzenberger.de>
To: Petr Baudis <pasky@suse.cz>
Cc: Wolfgang Denk <wd@denx.de>, git@vger.kernel.org
Subject: Re: git: problems in read-only trees
Date: Thu, 04 Aug 2005 22:38:36 +0200	[thread overview]
Message-ID: <42F27CCC.5050103@my-eitzenberger.de> (raw)
In-Reply-To: <20050804201125.GB24479@pasky.ji.cz>

Petr Baudis wrote:

>>-> cg-diff 
>>fatal: unable to create new cachefile
>>fatal: unable to create temp-file
>>
>>It would be nice if there was at least a way to specify  some  TMPDIR
>>instead of the current directory in such a situation.

> This is a bug in git-diff-* (producing the second error message; the first
> error message means failed git-update-cache --refresh but that isn't
> fatal). Any reason why prep_temp_blob() works in . instead of $TMPDIR?

I do not know about the first message (cachefile), but the 2nd one is 
trivial to fix.  I implemented a function called git_mkstemp() (path.c 
and so in libgit) which places the tmpfiles in $TMPDIR and if it's not 
set in /tmp.  The is close to what other programs do.

There are other references to mkstemp() in git where one or two of them 
may use git_mkstemp() instead, but not in sha1_file.c, since it 
hardlinks  it later on.

/holger

      reply	other threads:[~2005-08-04 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03  7:42 cogito: problems in read-only trees Wolfgang Denk
2005-08-04 20:11 ` git: " Petr Baudis
2005-08-04 20:38   ` Holger Eitzenberger [this message]

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=42F27CCC.5050103@my-eitzenberger.de \
    --to=holger@my-eitzenberger.de \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=wd@denx.de \
    /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.