From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org, Erik Sandberg <mandolaerik@gmail.com>
Subject: [StGit PATCH 0/2] Fix stg breakage with nweer gits
Date: Sat, 12 Apr 2008 17:47:15 +0200 [thread overview]
Message-ID: <20080412154427.19690.71877.stgit@yoghurt> (raw)
The new-infrastructure commands stopped working with newer gits, due
to git merge-recursive starting to heed GIT_WORK_TREE. Patch 1/2 fixes
this issue; patch 2/2 is some debugging stuff I built while tracking
down the bug.
Erik, this fixes your bug.
---
Karl Hasselström (2):
Log environment and cwd as well as the actual command
Don't both change directory and set GIT_WORK_TREE
stgit/lib/git.py | 14 +++++++++-----
stgit/run.py | 6 ++++++
2 files changed, 15 insertions(+), 5 deletions(-)
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle
next reply other threads:[~2008-04-12 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 15:47 Karl Hasselström [this message]
2008-04-12 15:47 ` [StGit PATCH 1/2] Don't both change directory and set GIT_WORK_TREE Karl Hasselström
2008-04-12 15:47 ` [StGit PATCH 2/2] Log environment and cwd as well as the actual command Karl Hasselström
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=20080412154427.19690.71877.stgit@yoghurt \
--to=kha@treskal.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=mandolaerik@gmail.com \
/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).