All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] doc: add AGENTS.md for AI coding assistants
Date: Wed, 28 Jan 2026 17:32:02 -0800	[thread overview]
Message-ID: <20260128173202.30cdcb58@phoenix.local> (raw)
In-Reply-To: <6f5f0afd-ded9-4438-9dc1-82483581489f@lunn.ch>

On Sat, 24 Jan 2026 23:29:45 +0100
Andrew Lunn <andrew@lunn.ch> wrote:

> On Sat, Jan 24, 2026 at 02:14:27PM -0800, Stephen Hemminger wrote:
> > I (and probably others) are experimenting with AI code review
> > and dumentation tools. It is worthwhile to have a baseline  
> 
> dumentation tools? I know we say code should be KISS when possible,
> but i did not know there were tools to help make our code dumb.
> 
>      Andrew

Guess which part I wrote..

  reply	other threads:[~2026-01-29  1:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-24 22:14 [PATCH iproute2-next] doc: add AGENTS.md for AI coding assistants Stephen Hemminger
2026-01-24 22:29 ` Andrew Lunn
2026-01-29  1:32   ` Stephen Hemminger [this message]
2026-01-30 23:46 ` Stephen Hemminger
2026-01-31 19:12 ` David Ahern
2026-01-31 19:40 ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260128173202.30cdcb58@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=andrew@lunn.ch \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.