debian-devel  

Messages by Thread

• • Re: Let's make 2025 a year when code reviews became common in Debian Gioele Barabucci
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Simon Josefsson
  • Re: Let's make 2025 a year when code reviews became common in Debian Philipp Kern
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Simon McVittie
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Otto Kekäläinen
  • Re: Let's make 2025 a year when code reviews became common in Debian Sam Hartman
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Gioele Barabucci
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Jeremy Stanley
  • Re: Let's make 2025 a year when code reviews became common in Debian Johannes Schauer Marin Rodrigues
  • Re: Let's make 2025 a year when code reviews became common in Debian Gioele Barabucci
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonathan Dowland
  • Re: Let's make 2025 a year when code reviews became common in Debian Colin Watson
  • Re: Let's make 2025 a year when code reviews became common in Debian Wookey
  • Re: Let's make 2025 a year when code reviews became common in Debian Otto Kekäläinen
  • Re: Let's make 2025 a year when code reviews became common in Debian Wookey
  • Re: Let's make 2025 a year when code reviews became common in Debian Sam Hartman
  • Re: Let's make 2025 a year when code reviews became common in Debian Colin Watson
  • +1 (Re: Let's make 2025 a year when code reviews became common in Debian) Holger Levsen
  • Re: Let's make 2025 a year when code reviews became common in Debian Gioele Barabucci
  • Re: Let's make 2025 a year when code reviews became common in Debian Sam Hartman
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Sam Hartman
  • Re: Let's make 2025 a year when code reviews became common in Debian Otto Kekäläinen
  • Re: Let's make 2025 a year when code reviews became common in Debian Wookey
  • Re: Let's make 2025 a year when code reviews became common in Debian Xiyue Deng
  • Re: Let's make 2025 a year when code reviews became common in Debian Colin Watson
  • Re: Let's make 2025 a year when code reviews became common in Debian Xiyue Deng
  • Re: Let's make 2025 a year when code reviews became common in Debian Philip Hands
  • Re: Let's make 2025 a year when code reviews became common in Debian Otto Kekäläinen
  • Re: Let's make 2025 a year when code reviews became common in Debian Chris Hofstaedtler
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Andrea Pappacoda
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Richard Lewis
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Otto Kekäläinen
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Christoph J. Scherr
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Christoph J. Scherr
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Fabio Fantoni
  • Re: Let's make 2025 a year when code reviews became common in Debian Christoph J. Scherr
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonathan Dowland
  • Re: Let's make 2025 a year when code reviews became common in Debian Antonio Terceiro
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Otto Kekäläinen
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonathan Dowland
• Bug#1093050: ITP: acstore -- Attribute Container store access library Hilko Bengen
• Bug#1093026: ITP: gnupg24 -- GNU Privacy Guard, a LibrePGP implementation Simon Josefsson
• Bug#1092863: ITP: opaque-store - store encrypted blobs of information online, protected by a password using the OPAQUE protocol Joost van Baal-Ilić
• Built-Using vs Static-Built-Using Simon Richter
  • Re: Built-Using vs Static-Built-Using Otto Kekäläinen
• Vulkan based tests Simon Richter
• Bug#1092958: ITP: llm-ollama -- LLM plugin providing access to models running on an Ollama server Antoine Beaupre
• Bug#1092942: ITP: lomiri-printing-app -- Printing app which consumes a PDF from content hub Mike Gabriel
• Bug#1092897: ITP: python-onnxscript -- naturally author ONNX functions and models using a subset of Python M. Zhou
• Bug#1092895: ITP: zig -- Imperative programming language easily mixed with C Nick Black (Public gmail account)
• Bug#1092894: ITP: nvm -- Node Version Manager ilivanilton rezende barros
• Bug#1092862: ITP: gnudip -- GNU Dyamic IP protocol server and client John Lines
  • Re: Bug#1092862: ITP: gnudip -- GNU Dyamic IP protocol server and client ah
• minisign support in uscan nick black
  • Re: minisign support in uscan nick black
  • Re: minisign support in uscan Simon Josefsson
  • Re: minisign support in uscan Yadd
  • Re: minisign support in uscan Simon Josefsson
  • Re: minisign support in uscan nick black
  • Re: minisign support in uscan Simon Josefsson
  • Re: minisign support in uscan nick black
• Bug#1092789: ITP: r-cran-reformulas -- GNU R package to work with random effects formulas Dirk Eddelbuettel
• Complete and unified documentation for new maintainers Fabio Fantoni
  • Re: Complete and unified documentation for new maintainers Andrey Rakhmatullin
  • Re: Complete and unified documentation for new maintainers gregor herrmann
  • Re: Complete and unified documentation for new maintainers Julien Plissonneau Duquène
  • Re: Complete and unified documentation for new maintainers Ahmad Khalifa
  • Re: Complete and unified documentation for new maintainers Andrey Rakhmatullin
  • Re: Complete and unified documentation for new maintainers Fabio Fantoni
  • Project-wide LLM budget for helping people (was: Re: Complete and unified documentation for new maintainers M. Zhou
  • Re: Project-wide LLM budget for helping people Philipp Kern
  • Re: Project-wide LLM budget for helping people (was: Re: Complete and unified documentation for new maintainers Andrey Rakhmatullin
  • Call for contributions to maintain existing documentation - Salsa makes it is easy! (was: Re: Complete and unified documentation for new maintainers Otto Kekäläinen
  • Re: Call for contributions to maintain existing documentation - Salsa makes it is easy! Ahmad Khalifa
  • Re: Call for contributions to maintain existing documentation - Salsa makes it is easy! Serafeim (Serafi) Zanikolas
  • Re: Call for contributions to maintain existing documentation - Salsa makes it is easy! Jonas Smedegaard
  • wiki.d.o on a git-backed engine Serafeim (Serafi) Zanikolas
  • Re: wiki.d.o on a git-backed engine Jonas Smedegaard
  • Re: wiki.d.o on a git-backed engine Jonathan Dowland
  • Re: wiki.d.o on a git-backed engine Jonas Smedegaard
  • Re: wiki.d.o on a git-backed engine Jeremy Stanley
  • Re: wiki.d.o on a git-backed engine Ahmad Khalifa
  • Re: wiki.d.o on a git-backed engine Jeremy Stanley
  • Re: wiki.d.o on a git-backed engine nick black
  • Re: wiki.d.o on a git-backed engine Jonathan Dowland
  • Re: wiki.d.o on a git-backed engine Kunal Mehta
  • Re: wiki.d.o on a git-backed engine Jonathan Dowland
  • Re: wiki.d.o on a git-backed engine Steve McIntyre
  • Re: wiki.d.o on a git-backed engine Jonas Smedegaard
  • Re: wiki.d.o on a git-backed engine Steve McIntyre
  • Re: wiki.d.o on a git-backed engine Jonas Smedegaard
  • Re: wiki.d.o on a git-backed engine Andrej Shadura
  • Re: wiki.d.o on a git-backed engine Jonas Smedegaard
  • Re: wiki.d.o on a git-backed engine Chris Hofstaedtler
  • Re: wiki.d.o on a git-backed engine Jonas Smedegaard
  • What's next for the Debian Wiki? (was Re: wiki.d.o on a git-backed engine) Jonathan Dowland
  • Re: Call for contributions to maintain existing documentation - Salsa makes it is easy! Jonathan Dowland
  • Re: Call for contributions to maintain existing documentation - Salsa makes it is easy! Jonathan Dowland
  • Re: Call for contributions to maintain existing documentation - Salsa makes it is easy! Jan Dittberner
  • Re: Call for contributions to maintain existing documentation - Salsa makes it is easy! Steve McIntyre
  • Re: Project-wide LLM budget for helping people (was: Re: Complete and unified documentation for new maintainers Otto Kekäläinen
  • Re: Project-wide LLM budget for helping people (was: Re: Complete and unified documentation for new maintainers Colin Watson
  • Re: Project-wide LLM budget for helping people (WAS: Re: Complete and unified documentation for new maintainers Andrew M.A. Cater
  • Re: Project-wide LLM budget for helping people (WAS: Re: Complete and unified documentation for new maintainers Ángel
  • Re: Project-wide LLM budget for helping people (was: Re: Complete and unified documentation for new maintainers M. Zhou
  • Re: Project-wide LLM budget for helping people Philipp Kern
  • Re: Project-wide LLM budget for helping people M. Zhou
  • Re: Project-wide LLM budget for helping people Helmut Grohne
  • Re: Project-wide LLM budget for helping people Simon Richter
  • Re: Project-wide LLM budget for helping people (was: Re: Complete and unified documentation for new maintainers Philip Hands
  • Re: Project-wide LLM budget for helping people (was: Re: Complete and unified documentation for new maintainers Andrey Rakhmatullin
  • Re: Project-wide LLM budget for helping people (was: Re: Complete and unified documentation for new maintainers Holger Levsen
• Bug#1092770: ITP: python-crypt-r -- A copy of the crypt module that was removed in Python 3.13 Bo YU
• Bug#1092763: RFP: elpa-empv -- Empv.el provides a better command of the mpv player utility from within emacs, than the existing elpa-mpv package k4r4b3y
• Thanks for sqv in apt Ian Jackson
• Bug#1092666: ITP: safetensors -- Simple, safe way to store and distribute tensors Mo Zhou
• Theme for Trixie: Ceratopsian in the installer Roland Clobus
  • Re: Theme for Trixie: Ceratopsian in the installer Aurélien COUDERC
• Bug#1092585: ITP: sos -- Set of tools to gather troubleshooting data from a system Arif Ali
• Bug#1092555: ITP: golang-k8s-component-base -- Toolkit for building Kubernetes components with shared utilities Arthur Diniz
• DEP17 /usr-move: most mitigations (M18) for aliased diversions (P3) are broken Helmut Grohne
  • Re: DEP17 /usr-move: most mitigations (M18) for aliased diversions (P3) are broken Helmut Grohne
  • Re: DEP17 /usr-move: most mitigations (M18) for aliased diversions (P3) are broken G. Branden Robinson
  • Re: DEP17 /usr-move: most mitigations (M18) for aliased diversions (P3) are broken Helmut Grohne
  • Re: DEP17 /usr-move: most mitigations (M18) for aliased diversions (P3) are broken Helmut Grohne
  • Re: DEP17 /usr-move: most mitigations (M18) for aliased diversions (P3) are broken Helmut Grohne
• Bug#1092485: ITP: fonts-maple-mono -- open source monospace font focused on smoothing your coding flow Weng Qizhi
• Bug#1092483: ITP: python-dataset -- database abstraction layer Alexandre Detiste
• Bug#1092460: ITP: highs -- high performance linear optimization software Shengqi Chen
• Bug#1092369: ITP: gdown -- Google Drive public file downloader Edward Betts
• getting ziggy with it nick black
  • Re: getting ziggy with it nick black
  • Re: getting ziggy with it Jonathan Carter
  • Re: getting ziggy with it Russ Allbery
  • Re: getting ziggy with it Julien Plissonneau Duquène
  • Re: getting ziggy with it nick black
  • Re: getting ziggy with it nick black
  • Re: getting ziggy with it Stéphane Glondu
• Bug#1092363: ITP: repolib -- Repository Management for APT in Python (Python 3) Thomas Ward
• Bug#1092362: ITP: libmegapixels -- Device abstraction library for Megapixels Arnaud Ferraris
• Bug#1092358: ITP: libdng -- Support library for generating DNG (Digital NeGative) files Arnaud Ferraris
• Bug#1092347: ITP: scifem -- Scientific Computing Tools for Finite Element Methods Drew Parsons
• Towards DEP-14 acceptance and recently proposed changes Raphael Hertzog
  • Re: Towards DEP-14 acceptance and recently proposed changes Julien Plissonneau Duquène
  • Re: Towards DEP-14 acceptance and recently proposed changes Julien Plissonneau Duquène
  • Re: Towards DEP-14 acceptance and recently proposed changes Marco d'Itri
  • Re: Towards DEP-14 acceptance and recently proposed changes Julien Plissonneau Duquène
  • Re: Towards DEP-14 acceptance and recently proposed changes Andrey Rakhmatullin
  • Re: Towards DEP-14 acceptance and recently proposed changes Julien Plissonneau Duquène
  • Re: Towards DEP-14 acceptance and recently proposed changes Marco d'Itri
  • Re: Towards DEP-14 acceptance and recently proposed changes Xiyue Deng
  • Re: Towards DEP-14 acceptance and recently proposed changes gregor herrmann
  • Re: Towards DEP-14 acceptance and recently proposed changes Raphael Hertzog
  • Re: Towards DEP-14 acceptance and recently proposed changes gregor herrmann
  • Re: Towards DEP-14 acceptance and recently proposed changes Chris Hofstaedtler
  • Re: Towards DEP-14 acceptance and recently proposed changes Lucas Nussbaum
  • Re: Towards DEP-14 acceptance and recently proposed changes Otto Kekäläinen
  • Re: Towards DEP-14 acceptance and recently proposed changes Gioele Barabucci
• Bug#1092287: ITP: joycond -- System service to use Nintendo joy-cons as joypads Marco Trevisan
• Bug#1092288: ITP: xchpst -- eXtended CHange Process STate Andrew Bower
• Bug#1092266: ITP: golang-github-jackc-pgerrcode -- constants for PostgreSQL error codes Simon Josefsson
• Bug#1092260: ITP: python-certstream -- Client library for talking to certstream servers Simon Josefsson
• Bug#1092218: ITP: certstream-server-go -- aggregates data from multiple certificate transparency logs Simon Josefsson
• Bug#1092211: ITP: libsfdo -- A collection of libraries which implement some of the freedesktop.org specifications Birger Schacht
• Building packages in the future. Santiago Vila
  • Re: Building packages in the future. Otto Kekäläinen
  • Re: Building packages in the future. Santiago Vila
  • Re: Building packages in the future. Santiago Ruano Rincón
  • Re: Building packages in the future. Otto Kekäläinen
  • Re: Building packages in the future. Chris Hofstaedtler
  • Re: Building packages in the future. Holger Levsen
  • Re: Building packages in the future. Simon McVittie
  • Re: Building packages in the future. Jakub Wilk
  • Re: Building packages in the future. Bastian Blank
  • Re: Building packages in the future. Holger Levsen
  • Re: Building packages in the future. Santiago Vila
  • Re: Building packages in the future. Paul Gevers
  • Re: Building packages in the future. Santiago Vila
• gettext 0.23.x Santiago Vila
  • Re: gettext 0.23.x Guillem Jover
  • Re: gettext 0.23.x Santiago Vila
  • Re: gettext 0.23.x Guillem Jover
  • Re: gettext 0.23.x Santiago Vila
  • Re: gettext 0.23.x Simon Josefsson
  • Re: gettext 0.23.x Guillem Jover

• Earlier messages
• Later messages