whitequark[cis] changed the topic of #amaranth-lang to: Amaranth hardware definition language · weekly meetings: Amaranth each Mon 1700 UTC, Amaranth SoC each Fri 1700 UTC · play https://amaranth-lang.org/play/ · code https://github.com/amaranth-lang · logs https://libera.irclog.whitequark.org/amaranth-lang · Matrix #amaranth-lang:matrix.org
Degi has quit [Ping timeout: 264 seconds]
Degi has joined #amaranth-lang
mindw0rk has quit [Read error: Connection reset by peer]
mindw0rk has joined #amaranth-lang
jfng[m] has quit [Quit: Idle timeout reached: 172800s]
Lord_Nightmare has quit [Quit: ZNC - http://znc.in]
Lord_Nightmare has joined #amaranth-lang
notgull has joined #amaranth-lang
notgull has quit [Ping timeout: 264 seconds]
Wanda[cis] has quit [Quit: Idle timeout reached: 172800s]
cr1901_ has joined #amaranth-lang
cr1901 has quit [Ping timeout: 240 seconds]
<tpw_rules> whitequark[cis]: is there a particular motivation to add .git_archival.txt to the amaranth-boards repo? it breaks reproducibility of the archives as the names in the file will change depending on PR and branch status etc
<tpw_rules> it is also not in any of the other repos and the change history is not particularly enlightening
<whitequark[cis]> setuptools_scm used it to make versioning work without weird overrides when using a github archive
<whitequark[cis]> pdm-backend cannot use it for anything
SpaceCoaster has quit [Quit: Bye]
SpaceCoaster has joined #amaranth-lang
<tpw_rules> ok, i'm guessing converting that repo is also on the roadmap. recognize it's a low priority
<whitequark[cis]> oh I just did not know it causes issues
<tpw_rules> would you like me to file an issue?
<whitequark[cis]> or send a PR
<tpw_rules> i don't think i know enough about python build systems to do the conversion, but i'll investigate