debian-devel  

Messages by Thread

• • Re: Change the expectation that emails should wrap at 80 characters Philipp Kern
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Roger Lynn
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Stephan Verbücheln
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Henrik Ahlgren
  • Re: Change the expectation that emails should wrap at 80 characters Andrea Pappacoda
  • Re: Change the expectation that emails should wrap at 80 characters Henrik Ahlgren
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Stephan Verbücheln
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Russ Allbery
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Stephan Verbücheln
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: nerd-sniping [was: Change the expectation that emails should wrap at 80 characters] Jeremy Sowden
  • Re: nerd-sniping [was: Change the expectation that emails should wrap at 80 characters] Holger Levsen
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Charles Plessy
  • Re: Change the expectation that emails should wrap at 80 characters Jeremy Stanley
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Jeremy Stanley
  • Re: Change the expectation that emails should wrap at 80 characters Stephan Verbücheln
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters James Lu
  • Re: Change the expectation that emails should wrap at 80 characters Andrey Rakhmatullin
  • Re: Change the expectation that emails should wrap at 80 characters Henrik Ahlgren
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Jeremy Stanley
  • Re: Change the expectation that emails should wrap at 80 characters The Wanderer
  • Re: Change the expectation that emails should wrap at 80 characters Giuseppe Sacco
  • Re: Change the expectation that emails should wrap at 80 characters gregor herrmann
  • Re: Change the expectation that emails should wrap at 80 characters Jonas Smedegaard
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Holger Levsen
  • Re: Change the expectation that emails should wrap at 80 characters Philip Hands
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Andreas Metzler
  • Re: Change the expectation that emails should wrap at 80 characters Philip Hands
  • Re: Change the expectation that emails should wrap at 80 characters The Wanderer
  • Re: Change the expectation that emails should wrap at 80 characters Bjørn Mork
  • Re: Change the expectation that emails should wrap at 80 characters Jonas Smedegaard
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan McDowell
  • Re: Change the expectation that emails should wrap at 80 characters James Lu
  • Re: Change the expectation that emails should wrap at 80 characters Charles Plessy
  • Re: Change the expectation that emails should wrap at 80 characters Julien Plissonneau Duquène
  • Re: Change the expectation that emails should wrap at 80 characters Marc Haber
  • please do not use text/markdown Timo Röhling
  • Re: please do not use text/markdown Jonas Smedegaard
  • Re: please do not use text/markdown Timo Röhling
  • Re: Change the expectation that emails should wrap at 80 characters Jeremy Stanley
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Timo Röhling
  • Re: Change the expectation that emails should wrap at 80 characters Stephan Verbücheln
  • Re: Change the expectation that emails should wrap at 80 characters Blair Noctis
  • Re: Change the expectation that emails should wrap at 80 characters Mario Limonciello
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Tollef Fog Heen
  • Re: Change the expectation that emails should wrap at 80 characters Christoph Berg
  • Re: Change the expectation that emails should wrap at 80 characters Antonio Terceiro
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Andrea Pappacoda
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Stephan Verbücheln
  • Re: Change the expectation that emails should wrap at 80 characters Carsten Schoenert
  • Re: Change the expectation that emails should wrap at 80 characters Paul Tagliamonte
  • Re: Change the expectation that emails should wrap at 80 characters Philipp Kern
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Julien Plissonneau Duquène
• Bug#1098954: ITP: liborson-charts-java -- A 3D chart library for Java applications (JavaFX, Swing or server-side). Christian Bayle
• Bug#1098955: ITP: libjfreesvg-java -- A fast, lightweight Java library for creating Scalable Vector Graphics (SVG) output. Christian Bayle
• Bug#1098952: ITP: libjfreepdf-java -- JFreePDF is a modular library for the Java platform that provides an implementation of the Graphics2D API that emits PDF. Christian Bayle
• Bug#1098934: ITP: ocaml-mirage-ptime -- libraries and module types for portable clocks Stéphane Glondu
• TC decision on avahi vs systemd-resolved - #1091864 Helmut Grohne
• Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Otto Kekäläinen
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Guillem Jover
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Arnaud Rebillout
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Otto Kekäläinen
  • Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Simon Richter
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Lorenzo
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st NoisyCoil
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Bastian Blank
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st NoisyCoil
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Bastian Blank
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Matthias Urlichs
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Bastian Blank
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Matthias Urlichs
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Otto Kekäläinen
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Chris Hofstaedtler
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Matthias Urlichs
  • Re: Salsa CI job 'missing-breaks' to be enabled by default starting March 1st Otto Kekäläinen
• Bug#1098893: ITP: passage -- fork of password-store using age as encryption backend Hoël Bézier
• we need to talk about gitattributes Julien Plissonneau Duquène
  • Re: we need to talk about gitattributes Sean Whitton
  • Re: we need to talk about gitattributes Julien Plissonneau Duquène
• Bug#1098858: ITP: atinout -- AT command executor and response capturer for modems Jongmin Kim
• Bug#1098851: ITP: flamelens -- interactive flamegraph viewer in the terminal Blair Noctis
• Bug#1098842: ITP: python-packbits -- PackBits encoder and decoder Edward Betts
• Bug#1098820: ITP: libip-geolocation-mmdb-perl -- module to read MaxMind DB files gregor herrmann
• Bug#1098766: ITP: golang-github-smallstep-pkcs7 -- PKCS #7 / Cryptographic Message Syntax Simon Josefsson
• Bug#1098764: ITP: glaze -- High-performance C++ JSON serialization library Carl Keinath
• Bug#1098744: ITP: rust-asn1-rs -- parser/encoder for ASN.1 BER/DER data Jonas Smedegaard
• Bug#1098740: ITP: roman-numerals -- utilities for manipulating well-formed Roman numerals in Python Dmitry Shachnev
• Bug#1098738: ITP: rust-x509-parser -- parser for the X.509 v3 format Jonas Smedegaard
• Re: Mandatory LC_ALL=C.UTF-8 during package building Chris Hofstaedtler
• Bug#1098719: general: Wellbeing Screen Time doesn't capture data Oleh
  • Bug#1098719: general: Wellbeing Screen Time doesn't capture data Tobias Frost
  • Processed: Re: Bug#1098719: general: Wellbeing Screen Time doesn't capture data Debian Bug Tracking System
• Bug#1098718: ITP: idjc -- graphical shoutcast/icecast client (reintroduced) Magnus Holmgren
• Bug#1098705: ITP: nginx-snippets -- Useful, commonly used nginx configuration snippets Thomas Ward
• Bug#1098695: ITP: chordv -- ChordV is a software that allows you to annotate a list of songs with chords in a Qt6 editor. Gilles Maire
  • Re: Bug#1098695: ITP: chordv -- ChordV is a software that allows you to annotate a list of songs with chords in a Qt6 editor. Salvo Tomaselli
• Bug#1098669: ITP: nvim-gruvbox -- gruvbox colorscheme for nvim Matthias Geiger
• Bug#1098641: ITP: micronucleus -- Bootloader designed for AVR ATtiny microcontrollers Mariana Arias
• Bug#1098523: ITP: appanvil -- graphical user interface for AppArmor Jack Ullery
• Bug#1098522: ITP: python-shamir-mnemonic -- reference implementation of SLIP-0039: Shamir’s Secret-Sharing for Mnemonic Codes Soren Stoutner
• Bug#1098505: ITP: clatd -- CLAT and SIIT-DC ER with many XLAT engines Daniel Gröber
• Bug#1098490: ITP: clatd -- CLAT and SIIT-DC ER with many XLAT engines Daniel Gröber
• Join us in Montreal on March 28th and 29th for a Bug Squashing Party! Louis-Philippe Véronneau
• Bug#1098438: ITP: python-simple-pid -- Simple and easy-to-use PID controller Alexander Sulfrian
• Bug#1098424: ITP: python-packageurl -- Package URL (purl) spec Python implementation Santiago Ruano Rincón
• Debian Policy 4.7.1.0 and program names Vincent Lefevre
  • Re: Debian Policy 4.7.1.0 and program names Michael Biebl
• Advice for directory to symlink transition Timo Röhling
  • Re: Advice for directory to symlink transition Simon Richter
  • Re: Advice for directory to symlink transition Andrey Rakhmatullin
• Bug#1098384: ITP: fonts-pepperandcarrot -- A collection of open fonts required for contributors to edit the Pepper&Carrot webcomic files. Raul G
• Bug#1098361: ITP: golang-github-ergochat-readline -- readline implementation in pure Go Guillem Jover
• Bug#1098310: ITP: sphinx-togglebutton -- Toggle page content and collapse admonitions in Sphinx Kathara Sasikumar
• Bug#1098309: ITP: qrca -- QR code scanner Salvo 'LtWorf' Tomaselli
• Bug#1098306: ITP: 81voltd -- Server-side implementation of the QMI IMS Data service Alexandre Viard
• Bug#1098276: ITP: nsnotifyd -- promptly run command on DNS zone changes Daniel Gröber
• Bug#1098262: ITP: haskell-regex-pcre2 -- A PCRE2 backend for the regex-base API. Pete Ryland
• GCC-15 mass bug filing. Charles Plessy
  • Re: GCC-15 mass bug filing. Chris Hofstaedtler
  • Re: GCC-15 mass bug filing. Aurélien COUDERC
  • Re: GCC-15 mass bug filing. Matthias Klose
  • Re: GCC-15 mass bug filing. Sune Vuorela
  • Re: GCC-15 mass bug filing. Michael Biebl
  • Re: GCC-15 mass bug filing. Sune Vuorela
  • Re: GCC-15 mass bug filing. Preuße , Hilmar
  • Re: GCC-15 mass bug filing. Sune Vuorela
  • Re: GCC-15 mass bug filing. Preuße , Hilmar
  • Re: GCC-15 mass bug filing. Lucas Nussbaum
  • Re: GCC-15 mass bug filing. Holger Levsen
  • Re: GCC-15 mass bug filing. Santiago Vila
  • Re: GCC-15 mass bug filing. Lucas Nussbaum
  • Re: GCC-15 mass bug filing. Holger Levsen
  • Re: GCC-15 mass bug filing. Marco d'Itri
  • Re: GCC-15 mass bug filing. Matthias Klose
  • Re: GCC-15 mass bug filing. Andrey Rakhmatullin
  • Re: GCC-15 mass bug filing. Michael Biebl
  • Re: GCC-15 mass bug filing. Colin Watson
  • +1, many thanks! (Re: GCC-15 mass bug filing.) Holger Levsen
  • Re: GCC-15 mass bug filing. Antonio Terceiro
  • Re: GCC-15 mass bug filing. Samuel Thibault
• Bug#1096151: ITP: python-briefcase -- Convert Python project to native application Josenilson Ferreira da Silva
• Bug#1096150: ITP: forwords -- A very simple but effective tool to learn foreign language words Alexander Fomin
  • Re: Bug#1096150: ITP: forwords -- A very simple but effective tool to learn foreign language words Salvo Tomaselli
  • Re: Bug#1096150: ITP: forwords -- A very simple but effective tool to learn foreign language words Alex Fomin
• Bug#1096146: ITP: python-pyramid-retry -- Retry policy for the Pyramid web framework Maximilian Engelhardt
• Bug#1096145: ITP: python-pylons-sphinx-themes -- Sphinx themes for Pylons related projects Maximilian Engelhardt
• Bug#1096137: ITP: golang-github-landlock-lsm-go-landlock -- A Go library for the Linux Landlock sandboxing feature Simon Josefsson
• Re: Bug#932103: RFP: fuidshift -- remap a filesystem tree to shift one set of UID/GID ranges to another Vincent Tondellier
• Bug#1096132: ITP: golang-github-code-hex-go-generics-cache -- Key:value store/cache library written in Go generics Martina Ferrari
• Bug#1096131: ITP: golang-github-r3labs-sse -- Server Sent Events server and client for Golang Nicolas Peugnet
• Re: Bug#1093192: #1093192 "ITS: vtgrab": no uploaders specified? Chris Hofstaedtler
  • Re: Bug#1093192: #1093192 "ITS: vtgrab": no uploaders specified? Tobias Frost
  • Re: Bug#1093192: #1093192 "ITS: vtgrab": no uploaders specified? Andreas Tille
• Bug#1096128: ITP: python-nbstripout -- strip output from Jupyter and IPython notebooks Francesco Ballarin
• Automatically detecting header-only libraries and setting Static-Built-Using automatically Michael R. Crusoe
• Bug#1096105: ITP: ggml -- Tensor library for machine learning Christian Kastner
• Bug#1096035: ITP: hare-json -- JSON support for hare Guilherme Puida Moreira
• Upstreams with "official" tarballs differing from their git Stéphane Glondu
  • Re: Upstreams with "official" tarballs differing from their git Daniel Gröber
  • Re: Upstreams with "official" tarballs differing from their git Jeremy Stanley
  • Re: Upstreams with "official" tarballs differing from their git kpcyrd
  • Re: Upstreams with "official" tarballs differing from their git Julien Plissonneau Duquène
  • Re: Upstreams with "official" tarballs differing from their git Julien Puydt
  • Re: Upstreams with "official" tarballs differing from their git Marco d'Itri
  • Re: Upstreams with "official" tarballs differing from their git Sean Whitton
  • Re: Upstreams with "official" tarballs differing from their git Colin Watson
  • Re: Upstreams with "official" tarballs differing from their git Julien Puydt
  • Re: Upstreams with "official" tarballs differing from their git Simon Josefsson
  • Re: Upstreams with "official" tarballs differing from their git Julien Plissonneau Duquène
  • Re: Upstreams with "official" tarballs differing from their git Julien Puydt
  • Re: Upstreams with "official" tarballs differing from their git Julien Plissonneau Duquène
  • Re: Upstreams with "official" tarballs differing from their git Julien Puydt
  • Re: Upstreams with "official" tarballs differing from their git Julien Plissonneau Duquène
  • Re: Upstreams with "official" tarballs differing from their git Holger Levsen
  • Re: Upstreams with "official" tarballs differing from their git Julien Puydt
  • Re: Upstreams with "official" tarballs differing from their git Sean Whitton
  • Re: Upstreams with "official" tarballs differing from their git Jeremy Stanley

• Earlier messages
• Later messages