Michael J Gruber <g...@drmicha.warpmail.net> writes:

> Signed-off-by: Michael J Gruber <g...@drmicha.warpmail.net>
> ---
> Just trying to make it clearer, and threw in an article or two.
> Also, tried to make the use of tenses a bit more uniform.


>  Documentation/RelNotes/1.8.0.txt | 48 
> ++++++++++++++++++++--------------------
>  1 file changed, 24 insertions(+), 24 deletions(-)
> diff --git a/Documentation/RelNotes/1.8.0.txt 
> b/Documentation/RelNotes/1.8.0.txt
> index cc460a4..a17f893 100644
> --- a/Documentation/RelNotes/1.8.0.txt
> +++ b/Documentation/RelNotes/1.8.0.txt
> @@ -4,11 +4,11 @@ Git v1.8.0 Release Notes
>  Backward compatibility notes
>  ----------------------------
> -In the next major release, we will change the behaviour of the "git
> +In the next major release, we will change the behavior of the "git
>  push" command.  When "git push [$there]" does not say what to push, we
> -have used the traditional "matching" semantics (all your branches were
> +have used the traditional "matching" semantics so far (all your branches were
>  sent to the remote as long as there already are branches of the same
> -name over there).  We will use the "simple" semantics, that pushes the
> +name over there).  We will now use the "simple" semantics, that pushes the
>  current branch to the branch with the same name only when the current
>  branch is set to integrate with that remote branch.  There is a user
>  preference configuration variable "push.default" to change this, and

"so far" sounds fine but "will now" feels a bit overkill.

All the rest looked good.  Thanks.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to