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

git-rebase dirty index and email address bug?

From
JGJohn Goerzen <jgoerzen@complete.org>
Date
Mar 1, 2008, 20:40 UTC
Message-ID
<slrnfsjfpo.3fl.jgoerzen@katherina.lan.complete.org>
Hi folks,

I have checked out a remote git repo. I have hacked on my local copy for the last two days. I have performed no merges or anything elese odd. Today I git fetched the remote, and then I tried to git rebase upstream/master. I had committed all outstanding changes first. My index was clean. It displayed:

First, rewinding head to replay your work on top of it... HEAD is now at 77f1a60... Merge branch 'trunk' Dirty index: cannot apply patches (dirty: public/dispatch.fcgi)

Tthat particular file was one that I added. It did not exist upstream either at my initial checkout, nor was it added upstream at any point since.

git status shows:

# Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # new file: public/dispatch.fcgi # # Untracked files: # (use "git add <file>..." to include in what will be committed) # # .dotest/

So I tried the git reset command on public/dispatch.fcgi, and also then deleted that file. I then tried git-rebase --continue, which displayed:

sed: can't read .dotest/info: No such file or directory sed: can't read .dotest/info: No such file or directory sed: can't read .dotest/info: No such file or directory Patch does not have a valid e-mail address.

I have no idea what sed is complaining about, but that last line is interesting. The upstream git repo I am monitoring was itself converted from an svn repo using, presumably, git-svn or git-svnimport. It lies at git://gitorious.org/redmine-git/mainline.git

Most patches have an author like this:
Author: jplang <jplang@e93f8b46-1217-0410-a6f0-8f06a7374b81>

Could one of the git tools be trying to parse this for some odd reason?

Or is something else going on here?
Next: John Goerzen
Message 1 of 8 in “git-rebase dirty index and email address bug?”
  1. John GoerzenMar 1, 2008
  2. John GoerzenMar 1, 2008
  3. Jeff KingMar 2, 2008
  4. John GoerzenMar 2, 2008
  5. Jeff KingMar 2, 2008
  6. John GoerzenMar 3, 2008
  7. Jeff KingMar 4, 2008
  8. John GoerzenMar 4, 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.