Re: Commited to wrong branch
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Sep 15, 2009, 13:46 UTC
- Message-ID
- <46a038f90909150646t25c48d7ar1cfe4052ad0bb3b6@mail.gmail.com>
- In-Reply-To
- <26ae428a0909150627n4e5935bcxdcdf0fdd33a44aa8@mail.gmail.com>
On Tue, Sep 15, 2009 at 3:27 PM, Howard Miller <howard@e-learndesign.co.uk> wrote:
> What's to stop me......... > > * The "wrong" branch just tracks a remote so I can just dump it once I > have this fixed - (delete it and recreate it?)
Absolutely perfect plan. In fact, there's a way to "sync" your local branch to the remote one:
git checkout X git reset origin/X
(assuming that the remote branch is 'origin/X')
> * after my 'reset' the files I have in my working copy (still the
> wrong branch) should be the latest version ('git reset' does not
> change the working copy I think?)correct (git reset --hard OTOH will discard your changes)
> * So can I grab these files (they are mostly new), checkout the > correct version, and just overwrite the existing files? I'll loose > some history but not much and I don't care
Oh... well if there were other changes to the same files in the other branch you could be carrying "other" changes. git diff to make sure you're committing what you want.
> Seems too easy :-)
It is :-)
m
-- martin.langhoff@gmail.com martin@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff