From: Johannes Sixt <j.sixt@viscovery.net>
To: Gerrit Pape <pape@smarden.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH amend] git-config: print error message if the config file cannot be read
Date: Fri, 12 Oct 2007 13:59:44 +0200 [thread overview]
Message-ID: <470F61B0.40907@viscovery.net> (raw)
In-Reply-To: <20071012114057.30803.qmail@12f4c67b8560e2.315fe32.mid.smarden.org>
Gerrit Pape schrieb:
>> You probably want to see an error message *only* if you have supplied
>> a file name with --file.
>
> I changed the patch to die() only if --file was sepcified, and errno is
> not 0.
Thanks. I can live with that. ;)
-- Hannes
prev parent reply other threads:[~2007-10-12 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 12:51 [PATCH] git-config: print error message if the config file cannot be read Gerrit Pape
2007-10-09 13:16 ` Johannes Schindelin
2007-10-09 13:30 ` Johannes Sixt
2007-10-12 11:40 ` [PATCH amend] " Gerrit Pape
2007-10-12 11:59 ` Johannes Sixt [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=470F61B0.40907@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pape@smarden.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).