unnecessary prefixes removed for gradients

[awebdeveloper]

based on http://caniuse.com/#search=grad css prefix for moz and old webkit removed

[zlatanvasovic]

What did you make with commit history? This looks bad.

[cvrebert]

Does the version of the Android Browser for Android Gingerbread fall under "old WebKit"?

[zlatanvasovic]

@cvrebert CanIUse says no. -webkit-linear-gradient is enough.

http://caniuse.com/#search=linear-gradient

[awebdeveloper]

@zdroid What the right way to send a PR

[juthilo]

@awebdeveloper We'd prefer one commit containing all the changes in this PR. Try squashing your commits into a single one locally (http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html) and then push the changes to update this PR automatically.

[zlatanvasovic]

@awebdeveloper @juthilo Look at http://zdroid.roon.io/rebases-and-fails.

Merging two smaller commits into a bigger one is bad way to add something, but when you have many commits after that you need to use merge strategies. Problem is that them make many errors.

A better way: amend changes to last commit instead of publish many commits than squashing them. This is specifically good for pull request. Example:

$ git commit --amend -C HEAD # amend it
$ git push -f # force update

That's it.

[mdo]

If all else fails, close this and open a new pull request.

[zlatanvasovic]

Yup. :)

[awebdeveloper]

So you guys want me to merge all these commits into one and submit a another PR

[zlatanvasovic]

How my brain thinks:

$ git reset HEAD^6 # or 7, idk number of commits
$ git add -A
$ git commit -m "..."
$ git push -f origin master

Better suggestion: close pull request, create topic branch and then edit code. Don't edit code on master, because of you'll break commit history later.

I will gladly help, if you need help. 😄

[mdo]

@awebdeveloper Yes, please. Single commits make it super easy to pinpoint a change and roll back if need be, or at the very least get a complete picture through Git's history.

Submit a new pull request with all these changes in one commit and we'll get it in there. <3

[cvrebert]

I've taken the liberty of preparing a new PR: #11694