AD S <a...@radianweb.com.au> writes: > Thanks for your detailed reply. That's very appreciated. Honestly, I'm > trying really hard to get my head around Git, but, for whatever > reason, it's just taking a long time to click with me. > > So, I guess what I was trying to do was your first example, the > 'Forced Commit'. Both myself and the remote repository have a copy of > an identical file. I make alterations to that file and want to replace > the version on the remote repo with mine.
No, based on how you write about what you want to do I suspect you want to: 1. Pull down all changes from the repo (`git pull` or `git fetch`). 2. Check out `master` from the repo (`git checkout`). 3. Replace the file in question with your copy. 4. Commit the changes (`git commit`). 5. Push your changes to the repo (`git push`). /M -- Magnus Therning OpenPGP: 0x927912051716CE39 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus You know, take Lisp. You know, it’s the most beautiful language in the world. At least up until Haskell came along. — Larry Wall -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
