From: Paul Mackerras <paulus@samba.org>
To: Max Kirillov <max@max630.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v5 0/3] gitk: save only changed configuration on exit
Date: Sun, 22 Mar 2015 14:39:15 +1100 [thread overview]
Message-ID: <20150322033914.GB14271@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <1425441498-29416-1-git-send-email-max@max630.net>
On Wed, Mar 04, 2015 at 05:58:15AM +0200, Max Kirillov wrote:
> The changes:
>
> * remove unused views_modified_names assignment
> * use if {[catch...] to check saving error
> * split error reporting from busy wait
>
> The busy wait parameters are unchanged, mostly because I did not have time yet to test them.
Thanks, applied, with some rewording of the commit messages, and I
updated the error message that is shown when a stale temporary config
file exists to what I suggested previously.
Paul.
prev parent reply other threads:[~2015-03-22 3:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 3:58 [PATCH v5 0/3] gitk: save only changed configuration on exit Max Kirillov
2015-03-04 3:58 ` [PATCH v5 1/3] gitk: write only changed configuration variables Max Kirillov
2015-03-04 3:58 ` [PATCH v5 2/3] gitk: report file saving error Max Kirillov
2015-03-04 3:58 ` [PATCH v5 3/3] gitk: synchronize config write Max Kirillov
2015-03-22 3:39 ` Paul Mackerras [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=20150322033914.GB14271@iris.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=max@max630.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 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).