From: Max Kirillov <max@max630.net>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org, Max Kirillov <max@max630.net>
Subject: [PATCH v3 0/2] gitk: save only changed configuration on exit
Date: Sun, 9 Nov 2014 09:56:59 +0200 [thread overview]
Message-ID: <1415519821-30172-1-git-send-email-max@max630.net> (raw)
Hi.
Used explivit changed flag for views instead of trace. Minor style fixes.
As I said, could not use namespace for older config read because they leak to
globals.
Max Kirillov (2):
gitk: write only changed configuration variables
gitk: synchronize config write
gitk | 115 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------
1 file changed, 104 insertions(+), 11 deletions(-)
--
2.0.1.1697.g73c6810
next reply other threads:[~2014-11-09 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 7:56 Max Kirillov [this message]
2014-11-09 7:57 ` [PATCH v3 1/2] gitk: write only changed configuration variables Max Kirillov
2014-11-09 7:57 ` [PATCH v3 2/2] gitk: synchronize config write Max Kirillov
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=1415519821-30172-1-git-send-email-max@max630.net \
--to=max@max630.net \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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).