lkml.org 
[lkml]   [2003]   [Apr]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ChangeLog suggestion
Hi John,

On Sat, Apr 26, 2003 at 07:52:19AM +0100, John Bradford wrote:
> > In each changelog entry, it would be really useful to include the
> > Message-ID of that email in a regex-parsable location. This way, if the
> > email was cced to lkml it would be possible for folks to track down the
> > actual patch.
> >
> > I'm not familiar with your scripts, but I'd be surprised if this were very
> > difficult to implement. At the same time, there are many cases of changelog
> > entries that read only 'USB' or something equally unhelpful, where there is
> > little chance that anyone could track down the corresponding patch. Having the
> > Message-ID in those cases would make all the difference in the world.
>
> The changelogs are generated by BitKeeper - couldn't we simply include
> a link that will let anybody[1] access the relevant changesets?
>
> [1] This can be via HTTP, and _doesn't_ require anybody to use
> BitKeeper in any way.

That would be ideal.

Be well,
Zack

>
> John.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/

--
Zack Brown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:35    [W:0.102 / U:0.652 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site