www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Rosenvold <krosenv...@apache.org>
Subject Re: Git, history, protection, and other topics
Date Wed, 04 Nov 2015 06:59:19 GMT
It would appear to me that some server-side solutions (stash comes to mind)
keep infinite track of all changes ever made. So even though git allows you
to force push, server still has unlimited history available. can we have
that ?


2015-11-04 5:08 GMT+01:00 David Nalley <david@gnsa.us>:

> Hi folks,
> So earlier today I sent an email to PMCs@ indicating that we had
> turned on disabled fast forward commits and branch/tag deletion across
> all of the ASF git repositories. [1]
> The crux of the problem is that infrastructure had set the expectation
> that certain branches and tags were protected from force pushes or
> branch/tag deletion.
> It was recently discovered that a large number of our projects were
> doing their main branch of development outside of these protected
> branches, and not using the release branch and tag scheme that would
> leave them protected.  Some, were using branches with names like
> 'develop' while others had $project_foo.
> As a short-term, interim step to allow us to meet the expectation that
> the main we blocked fast-forward pushes and branch/tag deletion until
> we can figure out the best way to adequately address the situation.
> I don't know whether or not the situation is best addressed via policy
> or technical means, but the discussion here is designed to discover
> what that should look like, so that we can move past the admittedly
> blunt, and likely disruptive measure that we introduced today.
> So; let the discussions begin.
> --David
> [1]
> https://git-wip-us.apache.org/docs/switching-to-git.html#protected-ref-lists

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message