-
-
Notifications
You must be signed in to change notification settings - Fork 884
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
Purge IE #451
Purge IE #451
Conversation
…ods were styling it away completely, probably not realizing they were disabling RES functionality by doing so. This name should be a little more clear. also adding additional body class, .res-v420, in case mods want to style differently against newest version.
…ole until they open it.
…RES users won't use it, hopefully that changes over time!)
…"actions" in the RES console can be created.
…y in RES settings this is so yucky. the settings console needs an MVC-style refactor.
honestbleeps, is there a reason you chose value before? it seems inappropriate for the button text to be the option value
any reason why !important?
…for bitcoin wallet
update modules.bitcoinTip with skeeto's refactoring, my refactoring, and my fixups
…ing this via !important on .entry … :-\
Mistakenly passed two classes to classList which returns a DOM Exception error. Removing superfluous class.
…RESUtils.addCsspostLoad
…r currently hover-info'd
instead of at the end, after [l+c]
blame skeeto for the whitespace changes 😁
…true after all modules .go()
Handle flickr lightbox links
…tUser Add highlight to user via [highlight] button on user tagger hover info
d'oh, this can't be automerged and it's gigantic... any chance you could rebase? I'm happy to get this in.. I won't pull any other requests before this one next time you submit it :-\ |
Ping @patricksnape. |
I just merged a different purge IE pr recently. On my phone so can't easily
|
I assume you mean 53564b3? Was that a purge (i.e. with force push) or just removing them from the head? Given it's 98MB on disk I assume the latter, hence pinging this issue. |
I just removed them from the head; I thought that'd be an improvement over the original repo. We still do need to rebase though. |
okay I must confess my git-fu is what I'd consider "intermediate" here... I On Sun, Sep 1, 2013 at 12:42 PM, Kevin Ji notifications@github.com wrote:
|
The commit rewrites history so that the IE commits never happened. Therefore, all the changes after I committed this need to be rebased on top of it and then master needs to be force pushed to the new |
Oh he was talking about rebasing your commit / pr. That makes more sense! I was imagining some magic "Rebase that crap out of here" thing and got
|
Running the following on your local machine should work (note: this will take some time to finish):
should do the trick. Then, to force push (and rewrite the repo's history), run:
AFTERWARDS, anyone else who had a repo before must force-rewrite their local and remote history (assuming that they're working with a fork). The easiest way is to delete your fork and re-fork the main project, then pull from your fork; however, if you do not wish to do that, follow the steps below:
If they have any branches, they must rebase them to the force-rewritten master first:
Then
And cleaning up their repo afterwards is a nice idea:
@patricksnape I don't think that my commit should be an issue; it's not empty at least (it contains a write to .gitignore) and the file removes should be purged from the history. |
the voodoo has been performed... will add a note to the readme.md right now about people with existing forks, thank you loads, @mc10 and @patricksnape |
@honestbleeps I think you nuked some of the commits from today.... uh oh. |
oh no.. I just ran your stuff verbatim! :-\ how much was lost off the top of your head? On Mon, Sep 2, 2013 at 4:46 PM, Kevin Ji notifications@github.com wrote:
|
That's weird, since my stuff shouldn't have affected it... are you sure you had an updated copy of the repo from the computer where you ran the commands? Also, I should have an up-to-date copy of the master branch in my repo, so perhaps you could force update your master from my repo, and try again? |
ugh, yeah I see it... is there a way to reopen those pull requests and or I could cherry pick the commits if need be... On Mon, Sep 2, 2013 at 4:46 PM, Kevin Ji notifications@github.com wrote:
|
Can't you just rease the range of commits that are missing back on top of the current HEAD? On Mon, Sep 2, 2013 at 10:50 PM, honestbleeps notifications@github.com
|
I may have forgotten to do a git pull before running those commands. crap. I'll have to try pulling in your master later as I'm on my way out :-\ On Mon, Sep 2, 2013 at 4:50 PM, Kevin Ji notifications@github.com wrote:
|
@patricksnape I'm not quite sure how you do that exactly... it'd be nice if you could tell us how.
Then, re-run the |
before I head out: the other 2 PRs that are lost would be really easy to What I could do is really just fetch the user.js file from your branch and On Mon, Sep 2, 2013 at 4:57 PM, Kevin Ji notifications@github.com wrote:
|
Maybe using rebase --onto? |
yeah, i just cherrypicked my #554 onto new master. |
Can you cherry pick the rest of the commits into master? |
I've cherry picked everything over, I believe we're good now! On Mon, Sep 2, 2013 at 7:15 PM, Kevin Ji notifications@github.com wrote:
|
So far as I can tell, this issue is now resolved. I just cloned the repo fresh and it took just a few seconds. |
Amazing, thanks. |
Purges the Debug and Release folders (#179, #448), in particular (sizes in kb):
In order to merge this it apparently HAS to be rebased - and so does ever single branch everyone currently has taken out. This is to prevent the old history being merged back in. However, since it's only IE files which nobody works on (or I don't know of anyone working on it), it shouldn't cause any conflicts.
The new head then has to be FORCE pushed back up to change the history. May also need to contact Github to tell them to purge the cash of those large files.