From: Paulius Zaleckas <paulius.zaleckas@gmail.com>
To: catalin.marinas@gmail.com, git@vger.kernel.org
Subject: [PATCH] StGit: export: fix base commit reporting in series file
Date: Sun, 21 Nov 2010 17:57:06 +0200 [thread overview]
Message-ID: <20101121155706.16544.20984.stgit@localhost.localdomain> (raw)
This bug was introduced in 3f19450c426970b78b19c522a82df1a962da5761
It should report the commit stg stack is based on, but not the
last patch in stack.
Signed-off-by: Paulius Zaleckas <paulius.zaleckas@gmail.com>
---
stgit/commands/export.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/stgit/commands/export.py b/stgit/commands/export.py
index 4285612..a661a7d 100644
--- a/stgit/commands/export.py
+++ b/stgit/commands/export.py
@@ -115,7 +115,7 @@ def func(parser, options, args):
# note the base commit for this series
if not options.stdout:
- base_commit = stack.patches.get(patches[0]).commit.sha1
+ base_commit = stack.base.sha1
print >> series, '# This series applies on GIT commit %s' % base_commit
patch_no = 1;
next reply other threads:[~2010-11-21 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 15:57 Paulius Zaleckas [this message]
2010-11-24 16:57 ` [PATCH] StGit: export: fix base commit reporting in series file 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=20101121155706.16544.20984.stgit@localhost.localdomain \
--to=paulius.zaleckas@gmail.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).