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

[StGit PATCH] Don't keep old committer when rewriting a commit

From
Karl Hasselström <kha@treskal.com>
Date
Jan 24, 2008, 08:09 UTC
Message-ID
<20080124080912.25671.67795.stgit@yoghurt>
Signed-off-by: Karl Hasselström <kha@treskal.com>
---
I think this is what the old infrastructure does too.
 stgit/lib/transaction.py |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/stgit/lib/transaction.py b/stgit/lib/transaction.py
index a60c5ff..809eabf 100644
--- a/stgit/lib/transaction.py
+++ b/stgit/lib/transaction.py
@@ -176,6 +176,7 @@ class StackTransaction(object):
         conflicts to them."""
         i = self.unapplied.index(pn)
         cd = self.patches[pn].data
+        cd = cd.set_committer(None)
         s = ['', ' (empty)'][cd.is_nochange()]
         oldparent = cd.parent
         cd = cd.set_parent(self.__head)
Message 1 of 1 in “Don't keep old committer when rewriting a commit”
  1. Don't keep old committer when rewriting a commitKarl Hasselström, Jan 24, 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.