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

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

From
Max Kirillov <max@max630.net>
Date
Sep 14, 2014, 20:35 UTC
Message-ID
<1410726959-20353-1-git-send-email-max@max630.net>
Changes since v1:
* Add value check to config_variable_change_cb
* Squash 2/3 and 3/3 and the value check into one commit. There is no really
  reasons to divide them except following the real coding history
* Describle the previous undesirable behavior in commit message
* Synchronize writing of config file
Max Kirillov (3):
  gitk refactor: remove boilerplate for configuration variables
  gitk: write only changed configuration variables
  gitk: synchronize config write
 gitk | 215 +++++++++++++++++++++++++++++++++++++++++++------------------------
 1 file changed, 139 insertions(+), 76 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 14, 2014
  2. 1/3 gitk refactor: remove boilerplate for configuration variablesMax Kirillov, Sep 14, 2014
  3. Paul MackerrasOct 30, 2014
  4. 2/3 gitk: write only changed configuration variablesMax Kirillov, Sep 14, 2014
  5. Paul MackerrasOct 30, 2014
  6. Max KirillovOct 30, 2014
  7. 3/3 gitk: synchronize config writeMax Kirillov, Sep 14, 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.