git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/3] gitk: save only changed configuration on exit

From
Max Kirillov <max@max630.net>
Date
Sep 11, 2014, 05:21 UTC
Message-ID
<1410412888-10187-1-git-send-email-max@max630.net>

gitk rewrites whole its config on exit. This is inconvenient when there are several instances running - if user changes something in one instance, it may be discarded depending of the order of closing that instances.

Change saving so that it saves only changed data and tried to preserve other existing data in configuration.

Max Kirillov (3):
  gitk refactor: remove boilerplate for configuration variables
  gitk: write only changed configuration variables
  gitk: merge views with existing ones
 gitk | 159 ++++++++++++++++++++++++++++++++++++-------------------------------
 1 file changed, 86 insertions(+), 73 deletions(-)
-- 
2.0.1.1697.g73c6810
Next: Max Kirillov
Message 1 of 7 in “gitk: save only changed configuration on exit”
  1. 0/3 gitk: save only changed configuration on exitMax Kirillov, Sep 11, 2014
  2. 1/3 gitk refactor: remove boilerplate for configuration variablesMax Kirillov, Sep 11, 2014
  3. 2/3 gitk: write only changed configuration variablesMax Kirillov, Sep 11, 2014
  4. Junio C HamanoSep 11, 2014
  5. Max KirillovSep 11, 2014
  6. Junio C HamanoSep 11, 2014
  7. 3/3 gitk: merge views with existing onesMax Kirillov, Sep 11, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.