On Wed, Jun 26, 2024 at 10:12:35AM GMT, Geert Uytterhoeven wrote:
> > > + Link: https://patch.msgid.link/patch-source-msgid@here
> >
> > Hmm, I mentioned this in the other thread, but I also like the fact
> > that my automated script uses the list that it was Cc'd to. That is, if
> > it Cc'd li
Hi Steven,
On Tue, Jun 25, 2024 at 11:27 PM Steven Rostedt wrote:
> On Tue, 18 Jun 2024 12:42:11 -0400
> Konstantin Ryabitsev wrote:
> > + A similar approach was attempted before as part of a different
> > + effort [1], but the initial implementation caused too many
> > + regressions
On Tue, 18 Jun 2024 12:42:11 -0400
Konstantin Ryabitsev wrote:
>
> diff --git a/Documentation/process/maintainer-tip.rst
> b/Documentation/process/maintainer-tip.rst
> index 64739968afa6..57ffa553c21e 100644
> --- a/Documentation/process/maintainer-tip.rst
> +++ b/Documentation/process/maintain
On 6/18/24 11:42, Konstantin Ryabitsev wrote:
> Based on multiple conversations, most recently on the ksummit mailing
> list [1], add some best practices for using the Link trailer, such as:
>
> - how to use markdown-like bracketed numbers in the commit message to
> indicate the corresponding link
On 18.06.24 18:42, Konstantin Ryabitsev wrote:
> Based on multiple conversations, most recently on the ksummit mailing
> list [1], add some best practices for using the Link trailer, such as:
>
> - how to use markdown-like bracketed numbers in the commit message to
> indicate the corresponding lin
On Wed, Jun 19, 2024 at 10:12:51AM GMT, Leon Romanovsky wrote:
> Default b4.linkmask points to https://msgid.link/ and not to
> https://patch.msgid.link/
That's the default for the b4 project itself, though, not the global default.
> https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/.b4-config
On Wed, Jun 19, 2024 at 11:50:48AM +0300, Jani Nikula wrote:
> On Tue, 18 Jun 2024, Konstantin Ryabitsev
> wrote:
> > Based on multiple conversations, most recently on the ksummit mailing
> > list [1], add some best practices for using the Link trailer, such as:
> >
> > - how to use markdown-like
On Wed, Jun 19, 2024 at 04:41:49AM -0400, Michael S. Tsirkin wrote:
> On Tue, Jun 18, 2024 at 12:42:11PM -0400, Konstantin Ryabitsev wrote:
> > Based on multiple conversations, most recently on the ksummit mailing
> > list [1], add some best practices for using the Link trailer, such as:
> >
> > -
On Tue, 18 Jun 2024, Konstantin Ryabitsev
wrote:
> Based on multiple conversations, most recently on the ksummit mailing
> list [1], add some best practices for using the Link trailer, such as:
>
> - how to use markdown-like bracketed numbers in the commit message to
> indicate the corresponding
On Tue, Jun 18, 2024 at 12:42:11PM -0400, Konstantin Ryabitsev wrote:
> Based on multiple conversations, most recently on the ksummit mailing
> list [1], add some best practices for using the Link trailer, such as:
>
> - how to use markdown-like bracketed numbers in the commit message to
> indicat
On Tue, Jun 18, 2024 at 12:42:11PM -0400, Konstantin Ryabitsev wrote:
> Based on multiple conversations, most recently on the ksummit mailing
> list [1], add some best practices for using the Link trailer, such as:
>
> - how to use markdown-like bracketed numbers in the commit message to
> indicat
On Tue, Jun 18, 2024 at 12:42:11PM -0400, Konstantin Ryabitsev wrote:
> Based on multiple conversations, most recently on the ksummit mailing
> list [1], add some best practices for using the Link trailer, such as:
>
> - how to use markdown-like bracketed numbers in the commit message to
> indicat
Based on multiple conversations, most recently on the ksummit mailing
list [1], add some best practices for using the Link trailer, such as:
- how to use markdown-like bracketed numbers in the commit message to
indicate the corresponding link
- when to use lore.kernel.org vs patch.msgid.link domai
13 matches
Mail list logo
