| 1 |
On 06/10/15 11:08, William Hubbs wrote: |
| 2 |
> On Tue, Jun 09, 2015 at 11:34:34PM -0400, Dean Stephens wrote: |
| 3 |
>> On 06/08/15 15:38, William Hubbs wrote: |
| 4 |
>>> All, |
| 5 |
>>> |
| 6 |
>>> here is the latest version of this eclass, which I will commit |
| 7 |
>>> an hour from now if no one has any objections. |
| 8 |
>>> |
| 9 |
>>> Thanks, |
| 10 |
>>> |
| 11 |
>>> William |
| 12 |
>>> |
| 13 |
>> Not an objection to the eclass as posted, but to the one hour |
| 14 |
>> timeout for feedback on a mailing list. While I realize that |
| 15 |
>> feedback had already been given and acted upon, bare minimum |
| 16 |
>> feedback windows for global mailing lists start at not less than |
| 17 |
>> 12 hours and are preferably at least twice that long. |
| 18 |
> |
| 19 |
> This hasn't been committed yet, because I'm considering adding a |
| 20 |
> command to copy the code from EGO_STORE_DIR to WORKDIR after it is |
| 21 |
> downloaded. |
| 22 |
> |
| 23 |
> Is a one line change enough to justify another poasting, or should |
| 24 |
> I just commit once that works? |
| 25 |
> |
| 26 |
> William |
| 27 |
> |
| 28 |
The answer to that would seem to be prescribed by policy[1]. |
| 29 |
|
| 30 |
[1] https://devmanual.gentoo.org/eclass-writing/index.html |
Archives