Skip to content

[MRG+1] minor edits to multiclass documentation#5837

Merged
jnothman merged 7 commits intoscikit-learn:masterfrom
pieteradejong:doc-edits-multiclass
Sep 30, 2016
Merged

[MRG+1] minor edits to multiclass documentation#5837
jnothman merged 7 commits intoscikit-learn:masterfrom
pieteradejong:doc-edits-multiclass

Conversation

@pieteradejong
Copy link
Copy Markdown
Contributor

minor changes to become familiar with the process

@pieteradejong
Copy link
Copy Markdown
Contributor Author

[MRG] ready to be merged, please review

@pieteradejong pieteradejong changed the title initial pull req: minor edits to multiclass documentation [MRG] minor edits to multiclass documentation Nov 16, 2015
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would keep the in.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure. http://english.stackexchange.com/questions/95929/consists-of-vs-consists-in-different-meanings-of-the-verb-or-the-same-mea http://english.stackexchange.com/questions/61600/consist-in-vs-consist-of

I think it is telling that the first hits for "consists in" are of stackexchange discussing the usage of the phrase.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "consists of" is better...

@TomDLT
Copy link
Copy Markdown
Member

TomDLT commented Nov 26, 2015

Nitpicks, but this looks good to me.
Thanks @pieteradejong

@TomDLT TomDLT changed the title [MRG] minor edits to multiclass documentation [MRG+1] minor edits to multiclass documentation Nov 26, 2015
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice catch ^^

@amueller
Copy link
Copy Markdown
Member

amueller commented Dec 9, 2015

please squash. LGTM apart from one comma, but I'm not a native speaker.

@pieteradejong
Copy link
Copy Markdown
Contributor Author

ready to merge?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be problems are restricted?

@TomDLT
Copy link
Copy Markdown
Member

TomDLT commented Jan 14, 2016

After final comments are addressed, could you also squash and rebase ?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say "which only considers binary classification". Currently the sentence is a bit awkward (what does "where" refer to?)

@amueller
Copy link
Copy Markdown
Member

otherwise lgtm, please squash.

@nelson-liu
Copy link
Copy Markdown
Contributor

now that we can rebase and squash in github, shall we do that here?

@TomDLT
Copy link
Copy Markdown
Member

TomDLT commented Sep 29, 2016

now that we can rebase and squash in github, shall we do that here?

There is no conflicts with master, so no need to rebase or squash.

@jnothman
Copy link
Copy Markdown
Member

There is still an open comment, though...

On 29 September 2016 at 19:41, Tom Dupré la Tour notifications@github.com
wrote:

now that we can rebase and squash in github, shall we do that here?

There is no conflicts with master, so no need to rebase or squash.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#5837 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEz66FFjv6tb26bn8hrB3bu4s8p2Nw1ks5qu4fhgaJpZM4GjPuL
.

@nelson-liu
Copy link
Copy Markdown
Contributor

Ah apologies didn't see the open comment, but only @amueller and @TomDLT asking for a squash (I presume this is before the github feature )

@amueller
Copy link
Copy Markdown
Member

Eh, let's merge and fix in master? The sentence was awkward before.

@jnothman jnothman merged commit 8442eea into scikit-learn:master Sep 30, 2016
@jnothman
Copy link
Copy Markdown
Member

Done, thanks @pieteradejong

TomDLT pushed a commit to TomDLT/scikit-learn that referenced this pull request Oct 3, 2016
* minor edits to multiclass documentation

* minor text formatting and language modifications

* minor word changes, sentence clarifications

* attempt to fix ci test

* restored previous paragraph

* minor grammatical correction

* minor grammar fixes
amueller pushed a commit to amueller/scikit-learn that referenced this pull request Oct 14, 2016
* minor edits to multiclass documentation

* minor text formatting and language modifications

* minor word changes, sentence clarifications

* attempt to fix ci test

* restored previous paragraph

* minor grammatical correction

* minor grammar fixes
Sundrique pushed a commit to Sundrique/scikit-learn that referenced this pull request Jun 14, 2017
* minor edits to multiclass documentation

* minor text formatting and language modifications

* minor word changes, sentence clarifications

* attempt to fix ci test

* restored previous paragraph

* minor grammatical correction

* minor grammar fixes
paulha pushed a commit to paulha/scikit-learn that referenced this pull request Aug 19, 2017
* minor edits to multiclass documentation

* minor text formatting and language modifications

* minor word changes, sentence clarifications

* attempt to fix ci test

* restored previous paragraph

* minor grammatical correction

* minor grammar fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants