From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] docs: link issue tracker
Date: Wed, 12 Nov 2025 11:10:32 +0100 [thread overview]
Message-ID: <aRRdGKd8xTkMJJUX@abai.de> (raw)
In-Reply-To: <20251112081549.134771-1-clara.kowalsky@siemens.com>
On 2025-11-12 09:15, 'Clara Kowalsky' via isar-users wrote:
> To make the issue tracker a bit more known, link it in the README.
Well, we've been actually directing all discussions towards isar-users as the
single channel of communication and archive. We had checked disabling issues
and PRs but seems it is not possible on github.
Issues do have the advantage of focus on the single topic, which mailing lists
address by archive threading. Are there other reasons why we should want to
encourage issues?
With kind regards,
Baurzhan
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/aRRdGKd8xTkMJJUX%40abai.de.
next prev parent reply other threads:[~2025-11-12 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 8:15 'Clara Kowalsky' via isar-users
2025-11-12 10:10 ` Baurzhan Ismagulov [this message]
2025-11-12 10:43 ` 'Clara Kowalsky' via isar-users
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=aRRdGKd8xTkMJJUX@abai.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox