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

[StGit PATCH 0/2] Patch stack logging

From
Karl Hasselström <kha@treskal.com>
Date
Feb 14, 2008, 01:25 UTC
Message-ID
<20080214012119.22365.54526.stgit@yoghurt>

So here's what I have this far. It writes a log that's close to the format I want, but doesn't do anything with it yet.

It's not in kha/experimental yet; it seems to work OK, but it leaves a log behind that'll have to be cleaned up manually when the format changes, which it will.

---
Karl Hasselström (2):
      Write to a stack log when stack is modified
      Library functions for tree and blob manipulation
 stgit/commands/branch.py   |   18 ++++--
 stgit/commands/clone.py    |    3 +
 stgit/commands/float.py    |    3 +
 stgit/commands/fold.py     |    3 +
 stgit/commands/imprt.py    |    3 +
 stgit/commands/init.py     |    3 +
 stgit/commands/pick.py     |    3 +
 stgit/commands/pop.py      |    3 +
 stgit/commands/pull.py     |    3 +
 stgit/commands/push.py     |    6 +-
 stgit/commands/rebase.py   |    4 +
 stgit/commands/refresh.py  |    4 +
 stgit/commands/rename.py   |    3 +
 stgit/commands/resolved.py |    4 +
 stgit/commands/sink.py     |    3 +
 stgit/commands/sync.py     |    5 +-
 stgit/lib/git.py           |  139 +++++++++++++++++++++++++++++++++++++-------
 stgit/lib/log.py           |   60 +++++++++++++++++++
 stgit/lib/transaction.py   |    3 +
 19 files changed, 229 insertions(+), 44 deletions(-)
 create mode 100644 stgit/lib/log.py
-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Next: Karl Hasselström
Message 1 of 8 in “Patch stack logging”
  1. 0/2 Patch stack loggingKarl Hasselström, Feb 14, 2008
  2. 1/2 Library functions for tree and blob manipulationKarl Hasselström, Feb 14, 2008
  3. 2/2 Write to a stack log when stack is modifiedKarl Hasselström, Feb 14, 2008
  4. Catalin MarinasFeb 20, 2008
  5. Karl HasselströmFeb 21, 2008
  6. Catalin MarinasFeb 22, 2008
  7. Karl HasselströmFeb 22, 2008
  8. Catalin MarinasFeb 22, 2008

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.