Fix some "Introduced in" inconsistencies

This commit is contained in:
Achilleas Pipinellis 2018-11-16 20:13:36 +01:00
parent 624ec62238
commit fbe3667ae2
No known key found for this signature in database
GPG Key ID: A0996FBD3E92C17B
1 changed files with 4 additions and 4 deletions

View File

@ -177,11 +177,11 @@ administrator to do so.
### Adding patches when creating a merge request via e-mail ### Adding patches when creating a merge request via e-mail
> **Note**: This feature was [implemented in GitLab 11.5](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22723) > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22723) in GitLab 11.5.
You can add commits to the merge request being created by adding You can add commits to the merge request being created by adding
patches as attachments to the email, all attachments with a filename patches as attachments to the email. All attachments with a filename
ending in `.patch` will be considered patches. The patches will be processed ending in `.patch` will be considered patches and they will be processed
ordered by name. ordered by name.
The combined size of the patches can be 2MB. The combined size of the patches can be 2MB.
@ -194,7 +194,7 @@ branch already exists, the patches will be applied on top of it.
## Find the merge request that introduced a change ## Find the merge request that introduced a change
> **Note**: this feature was [implemented in GitLab 10.5](https://gitlab.com/gitlab-org/gitlab-ce/issues/2383). > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/2383) in GitLab 10.5.
When viewing the commit details page, GitLab will link to the merge request (or When viewing the commit details page, GitLab will link to the merge request (or
merge requests, if it's in more than one) containing that commit. merge requests, if it's in more than one) containing that commit.