--=_courier-16211-1051378182-0001-2
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Sat, 2003-04-26 at 17:12, Zack Brown wrote:
> Hi John,
>=20
> 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 t=
he
> > > email was cced to lkml it would be possible for folks to track down t=
he
> > > actual patch.
> > >=20
> > > 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 cha=
ngelog
> > > entries that read only 'USB' or something equally unhelpful, where th=
ere 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.
> >=20
> > The changelogs are generated by BitKeeper - couldn't we simply include
> > a link that will let anybody[1] access the relevant changesets?
> >=20
> > [1] This can be via HTTP, and _doesn't_ require anybody to use
> > BitKeeper in any way.
>=20
> That would be ideal.
short of that there's the bk commit mailinglist that has all of them
anyway; it's 3 clicks in evolution to find one given the author ;)
--=_courier-16211-1051378182-0001-2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Transfer-Encoding: 7bit
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQA+qsGnxULwo51rQBIRAj69AKCGuAGQ2OenF/yIX37B7CtooPXaCwCffKpE
ymMECIEbUWXh1YUJ656zeNM=
=kqQT
-----END PGP SIGNATURE-----
--=_courier-16211-1051378182-0001-2--