From: Andy Green <andy@warmcat.com>
To: catalin.marinas@gmail.com
Cc: git@vger.kernel.org
Subject: StGIT munged path on refresh
Date: Mon, 04 Jun 2007 09:24:52 +0100 [thread overview]
Message-ID: <4663CC54.7090203@warmcat.com> (raw)
Hi folks -
I have been using quilt with some success and now I am trying to migrate
to stgit. I can get started okay with stg init and stg new "mypatch",
stg refresh then picks up modifications without having to be told about
the changed files, very nice.
However after I have modified several files in the tree, stg refresh
breaks without my having changed anything in the meantime to do with
stgit. The problem looks like this:
$ stg refresh
Checking for changes in the working directory... done
Refreshing patch "mISDN-remove-unused-test-from-bitops.patch"...error:
drivers/isdn/hardware/mISDN/drivers/isdn/hardware/mISDN/appl.c: does not
exist and --remove not passed
fatal: Unable to process file
drivers/isdn/hardware/mISDN/drivers/isdn/hardware/mISDN/appl.c
stg refresh: Failed git-update-index
$ pwd
/projects/octotux/packages/mISDN-1.2.0/drivers/isdn/hardware/mISDN
$ ls appl.c
appl.c
The tree starts at /projects/octotux/packages/mISDN-1.2.0, ie, there is
a .git/ in there. Notice that in the diagnostic, the path after the
start of the tree is repeated twice :-( but I did not run any stg or git
commands between a successful stg refresh and the first broken one.
In case it is important, I am working on a branch called "portability".
This is with
# rpm -q git-core
git-core-1.5.0.6-1.fc7
# rpm -q stgit
stgit-0.12.1-2.fc7
-Andy
next reply other threads:[~2007-06-04 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 8:24 Andy Green [this message]
2007-06-04 10:36 ` StGIT munged path on refresh Andy Green
2007-06-04 15:35 ` 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=4663CC54.7090203@warmcat.com \
--to=andy@warmcat.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).