Re: Consensus Call: Git Packaging Round 1
On Tue, Aug 27 2019, Antonio Terceiro wrote:
> FWIW, nowadays gitlab keeps track of every push, including rebases, to a
> single merge request. It even adds a "compare to previous version",
> where you can see the diff between the latest, maybe rebased, version of
> the branch, and the previous one.
>
> It _used_ to be the case that rebasing and force-pushing to the branch
> referenced by a merge request would make you lose the history, but that
> hasn't been true for a while.
That is a fundamental difference: it requires Gitlab to still be up to
access this history. As we have seen, both within our project and
outside, services like this don't necessarily live forever (see, for
instance, Google Code and Alioth).
One could, of course, say "yes but bugs.debian.org might not live
forever either!" True. But everything that goes through it is
mirrored in public in numerous places already. That history is, in
effect, safe.
As a conceptual matter, having some of the history of development be in
a git tree, and other history available only on a website, is a pretty
weird setup.
-- John
Reply to: