Skip to content

fixed little typo #4574

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

Merged
merged 1 commit into from
Dec 2, 2014
Merged

fixed little typo #4574

merged 1 commit into from
Dec 2, 2014

Conversation

adridev
Copy link
Contributor

@adridev adridev commented Dec 2, 2014

No description provided.

@xabbuh
Copy link
Member

xabbuh commented Dec 2, 2014

Good catch @adridev

@wouterj
Copy link
Member

wouterj commented Dec 2, 2014

Thanks, @adridev! (for the next time, it's better if you create a new branch for each PR, this means you can have multiple PRs at the same time)

@wouterj wouterj merged commit d43dacc into symfony:2.3 Dec 2, 2014
wouterj added a commit that referenced this pull request Dec 2, 2014
This PR was merged into the 2.3 branch.

Discussion
----------

fixed little typo

Commits
-------

d43dacc fixed little typo
@adridev
Copy link
Contributor Author

adridev commented Dec 2, 2014

Yes, I saw it in the docs but it is so little change that I skipped the creation of a new branch. Anyway I take note and the next time I will create a new branch. Thanks!

@xabbuh
Copy link
Member

xabbuh commented Dec 2, 2014

@adridev There no difference for the docs team whether or not you use a separate branch. But it's harder for you to create more than one pull request at the same time if you didn't.

@stof
Copy link
Member

stof commented Dec 2, 2014

it is also harder for you if the doc team rebases your PR to change the target branch, because you then have a diverging history in your fork.

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.

4 participants