Reorder README sections.

Reorder README sections.

This patch changes the order of README sections from:

 - checkout > build > sync > run

to:

 - checkout -> sync > build > run

R=etiennej@chromium.org, qsr@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/52764c404a222378b3a6edddf2f85b0811c62b86

[ppi, 2015-11-02 13:57:05]

Description was changed from

==========
Reorder README sections.

This patch changes the order of README sections from:

 - checkout > build > sync > run

to:

 - checkout -> sync > build > run
==========

to

==========
Reorder README sections.

This patch changes the order of README sections from:

 - checkout > build > sync > run

to:

 - checkout -> sync > build > run
==========

[ppi, 2015-11-02 13:57:05]

ppi@chromium.org changed reviewers:
+ etiennej@chromium.org, qsr@chromium.org

[ppi, 2015-11-02 13:57:15]

Hi Etienne or Ben,

ptal.

[etiennej, 2015-11-02 13:59:39]

https://codereview.chromium.org/1411133004/diff/1/README.md
File README.md (right):

https://codereview.chromium.org/1411133004/diff/1/README.md#newcode71
README.md:71: $ git pull --rebase
Rebase being optional, do we want to mention it here?

[ppi, 2015-11-02 14:09:15]

https://codereview.chromium.org/1411133004/diff/1/README.md
File README.md (right):

https://codereview.chromium.org/1411133004/diff/1/README.md#newcode71
README.md:71: $ git pull --rebase
On 2015/11/02 13:59:39, etiennej wrote:
> Rebase being optional, do we want to mention it here?

What happens when you have local changes on the branch and not pass `--rebase` -
wouldn't git then make the merge vs rebase call based on user settings? I assume
that we want to always rebase.

But I don't know really, http://xkcd.com/1597/

[qsr, 2015-11-02 14:17:03]

LGTM

(Etienne, I don't think a reformat CL is the right place to change the
documentation itself, for the baseline, rebase seems the better default option
given that we only push linear history)

[etiennej, 2015-11-02 14:26:10]

lgtm

https://codereview.chromium.org/1411133004/diff/1/README.md
File README.md (right):

https://codereview.chromium.org/1411133004/diff/1/README.md#newcode71
README.md:71: $ git pull --rebase
On 2015/11/02 14:09:15, ppi wrote:
> On 2015/11/02 13:59:39, etiennej wrote:
> > Rebase being optional, do we want to mention it here?
> 
> What happens when you have local changes on the branch and not pass `--rebase`
-
> wouldn't git then make the merge vs rebase call based on user settings? I
assume
> that we want to always rebase.
> 
> But I don't know really, http://xkcd.com/1597/

Acknowledged following offline discussion.

[ppi, 2015-11-02 14:27:11]

Committed patchset #1 (id:1) manually as
52764c404a222378b3a6edddf2f85b0811c62b86 (presubmit successful).