--AhhlLboLdkugWU4S
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hauke Fath <hf@spg.tu-darmstadt.de> wrote:

> Probably _any_ security related check-in to the pkgsrc trunk should=20
> automatically trigger a pullup request. ATM, it looks like this=20
> mostly happens 'on demand' via the tech-pkg list.

Hmm, how would one automate this, though?  The problem with pullup
requests are that they need to be tested on the stable branch as well as
on -current.  Not all security fixes can be easily applied without
modification or other changes being pulled up or merged.  This will
always require human intervention.

-Jan

--=20
"I am so amazingly cool you could keep a side of meat in me for a=20
month. I am so hip I have difficulty seeing over my pelvis."

--AhhlLboLdkugWU4S
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFCLarzfFtkr68iakwRAkIQAKCC7YUjz9osZIT7FM2cwRLqrelFaQCgr0jP
guzeE2Q9emh/FSLNxpF4438=
=QDSb
-----END PGP SIGNATURE-----

--AhhlLboLdkugWU4S--