link references in the merged patch

link references in the merged patch

[Michal Hocko]

Hi Andrew,
I was suggesting this during your mm workflow session at LSF/MM so this
is just a friendly reminder. Could you add something like tip tree and
reference the original email where the patch came from? Tip uses

Link: http://lkml.kernel.org/r/$msg_id

and this is really helpful when trying to find the discussion around the
patch. I would even welcome to add such a link for each follow up -fix*
patches and do
[ $email: $(comment for the follow up chaneg)]
Link: http://lkml.kernel.org/r/$msg_id

So it is clear what the follow up change was.

Thanks a lot!
-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

Re: link references in the merged patch

[Andrew Morton]

On Fri, 29 Apr 2016 10:16:02 +0200 Michal Hocko <mhocko@kernel.org> wrote:

> Hi Andrew,
> I was suggesting this during your mm workflow session at LSF/MM so this
> is just a friendly reminder. Could you add something like tip tree and
> reference the original email where the patch came from? Tip uses
> 
> Link: http://lkml.kernel.org/r/$msg_id
> 
> and this is really helpful when trying to find the discussion around the
> patch. I would even welcome to add such a link for each follow up -fix*
> patches and do
> [ $email: $(comment for the follow up chaneg)]
> Link: http://lkml.kernel.org/r/$msg_id
> 
> So it is clear what the follow up change was.
> 

Yeah, that's in my todo list (along with "do expense reports", sigh).
But who ever reads those things?

<fiddle fiddle>

OK, let's see how this goes.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

Re: link references in the merged patch

[Michal Hocko]

On Fri 29-04-16 14:06:28, Andrew Morton wrote:
> On Fri, 29 Apr 2016 10:16:02 +0200 Michal Hocko <mhocko@kernel.org> wrote:
> 
> > Hi Andrew,
> > I was suggesting this during your mm workflow session at LSF/MM so this
> > is just a friendly reminder. Could you add something like tip tree and
> > reference the original email where the patch came from? Tip uses
> > 
> > Link: http://lkml.kernel.org/r/$msg_id
> > 
> > and this is really helpful when trying to find the discussion around the
> > patch. I would even welcome to add such a link for each follow up -fix*
> > patches and do
> > [ $email: $(comment for the follow up chaneg)]
> > Link: http://lkml.kernel.org/r/$msg_id
> > 
> > So it is clear what the follow up change was.
> > 
> 
> Yeah, that's in my todo list (along with "do expense reports", sigh).
> But who ever reads those things?

I do quite often when I try to understand some subtle details which are
not clear from the changelog (that is not an exception) and the
discussion in the email thread sometimes helps. Plus it is good to see
where the fixups came from.

> <fiddle fiddle>
> 
> OK, let's see how this goes.

Thanks!

-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>