Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Message-ID: <1495359754.26536.2.camel@apache.org>
Subject: Re: [Httpcomponents Wiki] Update of "GitGuidelines" by MichaelOsipov
From: Oleg Kalnichevski <olegk@apache.org>
To: dev@hc.apache.org
Cc: Michael Osipov <michaelo@apache.org>
Date: Sun, 21 May 2017 11:42:34 +0200
In-Reply-To: <149535673274.30465.6173258254470747342@moin-vm.apache.org>
References: <149535673274.30465.6173258254470747342@moin-vm.apache.org>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
archived-at: Sun, 21 May 2017 09:42:40 -0000

On Sun, 2017-05-21 at 08:52 +0000, Apache Wiki wrote:
> Dear Wiki user,
> 
> You have subscribed to a wiki page or wiki category on
> "Httpcomponents Wiki" for change notification.
> 
> The "GitGuidelines" page has been changed by MichaelOsipov:
> https://wiki.apache.org/HttpComponents/GitGuidelines?action=diff&rev1
> =7&rev2=8
> 
> Comment:
> RM's right to rewrite
> 
>   
>   =  Side Notes =
>   
> -  1. Never rewrite (rebase) history on master or any other long-
> lived branch because you will break others
> +  1. Never rewrite (rebase) history on master or any other long-
> lived branch because you will break others. Only the release manager
> is entitled to clean up history right before a release if it is
> absolutely necessary

Hi Michael,

If the main motivating factor for not rewriting commits policy is to
minimize conflicts with work of casual contributors it would be better
to let the RM rewrite the very tip of a release branch on ongoing basis
instead of having the commit history mutate 3 to 6 months back in time
every time a release is cut.

Please reconsider.

Oleg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org