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

Re: I've tried to read the manuals, but "git pull" just won't work

From
MPMatt Pearson <404emailnotfound@gmail.com>
Date
Aug 3, 2008, 05:21 UTC
Message-ID
<706b4240808022221we345b13md95e0dacf9436dba@mail.gmail.com>
In-Reply-To
<668c430c0808022158s56e22c56t3bbd61eef59d7b32@mail.gmail.com>
On Sun, Aug 3, 2008 at 12:58 AM, Bruce Korb <bruce.korb@gmail.com> wrote:
Show 8 quoted lines
> Sorry, I don't know where else to turn.
> I've modified my local copy of ChangeLog and my "git pull" says, "Oh, oh!
> You'd overwrite your changes" and refuses to pull.  I tried
> "git reset HEAD  ChangeLog", but it says all sorts of crazy things
> that make no sense and I'm still stuck.  I know I can fix this:
> pull my edits into a patch, throw away my repository, clone a fresh
> copy.  There has to be a better way.  The better  way is just too
> obtuse to figure out.....Help, please?  Thank you.

Depends on whether you want to keep the changes you made or not. If you don't care about the changes, 'git checkout -- ChangeLog' will remove the local changes. If you want to keep the changes, you can stash them away with 'git stash', then do the pull, then re-add the changes (and maybe have to resolve conflicts) with 'git stash apply'. You could also just commit the changes. If you still can't get it to work, you're going to have to paste actual program output (the output from status would probably help).

Matt
Previous: Bruce Korb
Message 2 of 2 in “I've tried to read the manuals, but "git pull" just won't work”
  1. Bruce KorbAug 3, 2008
  2. Matt PearsonAug 3, 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.