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

StGIT munged path on refresh

From
Andy Green <andy@warmcat.com>
Date
Jun 4, 2007, 08:24 UTC
Message-ID
<4663CC54.7090203@warmcat.com>
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: Andy Green
Message 1 of 3 in “StGIT munged path on refresh”
  1. Andy GreenJun 4, 2007
  2. Andy GreenJun 4, 2007
  3. Catalin MarinasJun 4, 2007

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.