From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Fredrik Tolf <fredrik@dolda2000.com>
Cc: git@vger.kernel.org
Subject: Re: git-config: replaces ~/.gitconfig symlink with real file
Date: Tue, 17 Jul 2007 21:48:08 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707172145590.14781@racer.site> (raw)
In-Reply-To: <m3wswyojj2.fsf@pc7.dolda2000.com>
Hi,
On Tue, 17 Jul 2007, Fredrik Tolf wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > On Mon, 16 Jul 2007, Bradford Smith wrote:
> >
> >> So, I guess I need to add a GIT_CONFIG_HOME environment variable. If I
> >> get that done, I'll send a patch to the list including doc updates.
> >
> > Alternatively, you could actually not ignore my hint at readlink(2) and
> > have a proper fix, instead of playing games with environment variables.
>
> Wouldn't it be nicer to avoid a lot of the complexity in checking
> symlinks, environment variables and what not, and just overwrite the
> file in place (with open(..., O_TRUNC | O_CREAT))? Does it happen
> terribly often that git-config crashes in the middle and leaves the file
> broken?
No, it does not. But when it does, I am not only annoyed. I am PISSED!
The way we do it is the only safe way to do it, and I gladly spend some
extra cycles for that. Too often, a small hard disk glitch (or just an
empty laptop battery!) took some important data into the void. Too often,
I _cursed_ at the machine, even if it was the programmers' fault.
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-17 20:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 21:27 git-config: replaces ~/.gitconfig symlink with real file Bradford Smith
2007-07-15 23:30 ` Johannes Schindelin
2007-07-16 9:37 ` Nikolai Weibull
2007-07-16 11:33 ` Bradford Smith
2007-07-16 13:26 ` Bradford Smith
2007-07-16 22:46 ` Junio C Hamano
2007-07-25 16:49 ` [PATCH 0/2] git-config should not replace symlink Bradford C. Smith
2007-07-25 16:49 ` [PATCH 1/2] resolve symlinks when creating lockfiles Bradford C. Smith
2007-07-25 16:49 ` [PATCH 2/2] use lockfile.c routines in git_commit_set_multivar() Bradford C. Smith
2007-07-25 23:35 ` [PATCH 1/2] resolve symlinks when creating lockfiles Junio C Hamano
2007-07-26 16:55 ` [PATCH] use lockfile.c routines in git_commit_set_multivar() Bradford C. Smith
2007-07-26 18:31 ` Johannes Schindelin
2007-07-26 18:48 ` Bradford Smith
2007-07-27 4:30 ` Junio C Hamano
2007-07-27 4:53 ` Junio C Hamano
2007-07-27 9:05 ` Johannes Schindelin
2007-07-27 18:24 ` Bradford Smith
2007-07-26 17:34 ` [PATCH] fully resolve symlinks when creating lockfiles Bradford C. Smith
2007-07-26 18:35 ` Johannes Schindelin
2007-07-26 19:34 ` Morten Welinder
2007-07-27 16:50 ` Bradford Smith
2007-07-27 7:05 ` Junio C Hamano
2007-07-17 13:56 ` git-config: replaces ~/.gitconfig symlink with real file Johannes Schindelin
2007-07-17 14:27 ` Matthieu Moy
2007-07-17 20:35 ` Fredrik Tolf
2007-07-17 20:48 ` Johannes Schindelin [this message]
2007-07-17 13:39 ` Catalin Marinas
2007-07-17 16:09 ` 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=Pine.LNX.4.64.0707172145590.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=fredrik@dolda2000.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).