Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WTF ... really #290

Merged
merged 2 commits into from Apr 2, 2013
Merged

WTF ... really #290

merged 2 commits into from Apr 2, 2013

Conversation

Spuds
Copy link
Contributor

@Spuds Spuds commented Apr 1, 2013

OK I think this puts these two new templates back to what was in the latest version of those templates that they were grabbed from ... its great how github will simply overwrite an old file with a new one, super deluxe really

Also updated another in my long line of spellng errors (yes that one is on purpose)

… last merge undid a bunch of work ... tl;dr github sucks

Signed-off-by: Spuds <spuds@spudsdesign.com>
Signed-off-by: Spuds <spuds@spudsdesign.com>
@norv
Copy link
Contributor

norv commented Apr 2, 2013

We can merge this if you like; it seems correct that something got messed up, I'm not sure I get how this happened.. And I didn't test this but the code diff looks as expected at a quick check.

@Spuds
Copy link
Contributor Author

Spuds commented Apr 2, 2013

Bah ... For all I know I'm just delusional at this point and whats there is right ! I can't get some things to work in my local and it claims to match the master, yet they work on the site .... about ready to nuke everything local and start over!

@norv
Copy link
Contributor

norv commented Apr 2, 2013

Instead of nuke, I'd just clone in some other directory to check.

(of course, this is how I get a dozen repos and 3-30 branches in each, which I haz no clue where they are and why they are anymore, but hey!)

Actually for all I see your html5 changes did get missed - presumably when I split the files, but... it shouldn't have done that. (lol)

On another note: you can always reset your local branch to sometime long back in time, then pull from elk master.
i.e. git reset --hard [a hash from a few days ago]
Just make sure you commit or stash your current changes before, because reset --hard ain't joking, it does overwrite/remove everything current.

norv added a commit that referenced this pull request Apr 2, 2013
@norv norv merged commit cae4d0a into elkarte:master Apr 2, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants