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

Re: git apply won't work

From
BDBryan Donlan <bdonlan@gmail.com>
Date
Mar 13, 2009, 00:09 UTC
Message-ID
<3e8340490903121709w6c6c444o10e7c8b655246373@mail.gmail.com>
In-Reply-To
<a6d7dc140903121614s229ce97an2cb5737ef46c0421@mail.gmail.com>

On Thu, Mar 12, 2009 at 7:14 PM, Martin Paraskevov <martin.paraskevov@gmail.com> wrote:

Show 22 quoted lines
> Hi all,
>
> I did the following:
>
> edited
> did commit 1
> edited
> did commit 2
> edited
> did commit 3
>
> Now I want to patch the changes between 2 and 3 onto 1, i.e. have commit 3 but
> with the changes from commit 2 removed. I created a branch where I reset
> it to commit 1 and then tried to apply the diff between 3 and 2.
>
> The patch however won't patch certain files. It contains the excerpt below,
> for example, so it should be patching directory.c but it isn't. The command
> I'm running is just:
>
> % git apply filesys.patch
>
> What am I doing wrong?

It's hard to say what's going wrong when we can't see the exact errors, git tree and patch in question, but if you just want to remove a patch, there are easier ways to do it.

If you want to keep the old patch in the history, but reverse it, do:
  git revert commitid
This will record a new commit that reverses the changes in the
indicated one. This is the recommended way to do things if others have
based work off your branch.
If you want to completely forget about the patch in question, you can
do this using git rebase --interactive:
  git rebase --interactive commitid~
  (an editor will open; remove the patch in question from the list,
save and exit your editor)
  (fix any conflicts that come up as prompted)
This will delete it from history, but will result in commit IDs for
commits after that point changing. If anyone has based work off your
branch, then you might have a hard time merging later.
Previous: Martin Paraskevov
Message 2 of 2 in “git apply won't work”
  1. Martin ParaskevovMar 12, 2009
  2. Bryan DonlanMar 13, 2009

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.