Re: Core statement on version control systems

[Greg Troxel <gdt%lexort.com@localhost>]

Andreas Gustafsson <gson%gson.org@localhost> writes:

> At the risk of repeating what I said on tech-repository five years ago in
> https://mail-index.netbsd.org/tech-repository/2019/10/31/msg000673.html
> the hard part is the HTML reports, which are divided into monthly
> sections (graphs and lists of commits and builds).  To determine which
> monthly section a given commit should appear in, bracket needs to know
> when it was pushed to the public NetBSD repository, not when it was
> first committed to a developer's private repository.

Let me just pile on to say that as a human, I want to know when things
are merged into the official repo.

In a project I oversaw long ago, we expected all work to be on branches,
and then to have explict merge commits.  That way it was labeled who
created the commits and who approved merging them.  While the merge
commit date is technically not the push date, it's generally close.
This sounds awkward, but really it isn't.

(This led to rebasing before merge, both to fold in fixups, and to make
the history easier to follow, and of course prohibiting 'git pull'
backwards merges.)