From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [StGit PATCH 0/2] Patch stack logging
Date: Thu, 14 Feb 2008 02:25:08 +0100 [thread overview]
Message-ID: <20080214012119.22365.54526.stgit@yoghurt> (raw)
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 reply other threads:[~2008-02-14 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 1:25 Karl Hasselström [this message]
2008-02-14 1:29 ` [StGit PATCH 1/2] Library functions for tree and blob manipulation Karl Hasselström
2008-02-14 1:32 ` [StGit PATCH 2/2] Write to a stack log when stack is modified Karl Hasselström
2008-02-20 22:46 ` Catalin Marinas
2008-02-21 7:18 ` Karl Hasselström
2008-02-22 14:05 ` Catalin Marinas
2008-02-22 14:56 ` Karl Hasselström
2008-02-22 15:58 ` Catalin Marinas
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=20080214012119.22365.54526.stgit@yoghurt \
--to=kha@treskal.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.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).