Re: Core statement on version control systems

[Andreas Gustafsson <gson%gson.org@localhost>]

I only recently stumbled across the mail from January where Taylor wrote:
> Bracket is unhappy with non-linear commit dates but it can probably be
> made to use hg bisect instead.

Bracket will indeed be unhappy if commits no longer have monotonically
increasing timestamps, but the problems are unrelated to bisection.

Bisection is the easy part, because it is not concerned with time,
only with ordering, and that is well defined by the topological order
of the commits.

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.

Taylor also wrote:
>   XXX Future change: auditlog configured to record who pushed what
>   XXX (currently using deprecated pushlog instead)

Will the information in the pushlog or auditlog be publicly available
in a form suitable for automated use?  And if so, is there some test
repository already making this information available for testing
purposes?
-- 
Andreas Gustafsson, gson%gson.org@localhost