~teymour

null pointer

https://reasoning.page

...

~teymour/compiler-discuss

Last active 5 days ago

~teymour/compiler-devel

Last active 5 days ago

~teymour/compiler-announce

Last active 5 days ago

~teymour/mezzotint-discuss

Last active 6 days ago

~teymour/mezzotint-devel

Last active 6 days ago

~teymour/mezzotint-announce

Last active 6 days ago
View more

Recent activity

Re: Not rocket science rule 4 days ago

From Teymour Aldridge to ~sircmpwn/sr.ht-discuss

> Users/downstream should not pull from development branches,
> but tagged releases.  You can have a branch pointing to
> the latest release if VCS is preferred over tarballs.

The idea is to not have "development" branches - instead any commits 
which are merged into the main branch should be of sufficient quality to 
be deployed. Effectively this is a system of continuous delivery. This 
is not uncommon, either; many web services have their servers configured 
to automatically pull, build and deploy the latest commits from the main 
branch. Another such system is described in 
https://www.youtube.com/watch?v=tISy7EJQPzI.

> If a team consists of multiple engineers, patches should be reviewed
> (including tested) before applied.  If you fear human errors,

Not rocket science rule 5 days ago

From Teymour Aldridge to ~sircmpwn/sr.ht-discuss

Does anybody know if Sourcehut has support for/implements a system where 
it is possible to ensure that the primary branch of the repository of 
the system will never fail the tests (provided they are deterministic)?

For example, something like the one Rust uses (called bors): 
https://graydon2.dreamwidth.org/1597.html

-- 
Kind regards,
Teymour