Re: What to do with setup_{host, target, build}_hook and cleanup_target_hook procedures?
Ben Elliston <[email protected]>
| Newsgroups | gmane.comp.sysutils.dejagnu.general |
|---|---|
| Message-ID | <20190204054132.GA8879@bapbop> |
On Sun, Feb 03, 2019 at 10:27:20PM -0600, Jacob Bachmeyer wrote: > This issue with the code was found while writing documentation, so > the new documentation will at the least be included in the big > documentation patch I am currently working on. Should these code > changes also be rolled into that patch, submitted separately with > the revisions to the documentation held pending, or submitted > together with their specific new documentation to be merged > separately from (and prior to) the large patch? I favour option 3, please. That way, the changeset is kept all together in one commit. You should not find it very difficult to merge the other documentation changes in later. Cheers, Ben _______________________________________________ DejaGnu mailing list [email protected] https://lists.gnu.org/mailman/listinfo/dejagnu
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEENSRiQfm6HKSVS9n7K6SL/BBhB5UFAlxX0IsACgkQK6SL/BBh B5XT4w/8DKi8EUMGuricg1jVxCIbO/7ZW21LIY5Zg7AVSKhjfj04oA31qmSzGyUX M2/rjkqwl4zgJPb4syePR6m/jXpvEtKbc0HlKOnHsQvPw0givp2q+fY0c1Gz5li7 sbcJPVVJ46YqS5B6mxgFzS349Jk5i76U6VAI1JCsLCO+pxQh8POx61mZR3+U1Xt8 WkmL0Mp/wLkJNO4Vw9jdCKdQjNL5ul8wUoYvzlFpS+kzetmHZah5b4mGxeHjl0Yf MNW2g6INTS6m0AmVuSENygOt07ORnB66U5LYQZsD1v6KwinWG1/NoAMngvNii4pe g6l+6koXmFC8he1233GRCzjd7Kd/PJYkSFc1DJmwkF6GXGffAUgemhTWlaWTZgoG D9EVnZo/BTtPniOMzprhm9Zy+KI7bTuQBjw4pIH2kR9/6NVxSOl/B9EE6AYFHyAP k8UXrnADvj+I/z7YOuQzWNUTsicrHFMkCDXCbAxgs4ISxXL5F1gNb/XX9yzCNaBH gBGCvvgTXR8TS8CvhYUb0ICvsNmfMPikYL6dHQxKoF23ARU2mEINon+MzM65Lw2J rLgGQ6lk9PEh2cMQB7uwKTRKaR8Lb554bmpqsIq1ywsNJswrrvpBkK8TLIcIgBXD dloj4bEti9kCqPcdqNLO3aCftz4gGY06+ruoB5zlmBICdwzVgiA= =BWJZ -----END PGP SIGNATURE-----