| 1 |
On Donnerstag 03 November 2011 10:16:53 Michael Haubenwallner wrote: |
| 2 |
> |
| 3 |
> Again for 'emerge --changelog': |
| 4 |
> |
| 5 |
> As we do have the "$delay before breaking old" period, usually with |
| 6 |
> $delay="1 year": Should we also apply this $delay to the output of above |
| 7 |
> command? |
| 8 |
> |
| 9 |
> If yes, what I can think of ATM is: |
| 10 |
> * Do that first splitting in January 2012 (in less than 2 months). |
| 11 |
> * Have PM search in the old ChangeLogs if necessary. |
| 12 |
> |
| 13 |
> The latter would also allow for completely emptying current ChangeLog each |
| 14 |
> January by moving that to ChangeLog-$lastyear. |
| 15 |
> |
| 16 |
|
| 17 |
Makes all perfect sense... however I suggest to agree on a general scheme and |
| 18 |
go ahead manually first if implementation and/or discussion of its details or |
| 19 |
planned features is lingering... |
| 20 |
|
| 21 |
As opposed to EAPI features, this here is one of the cases where "availability |
| 22 |
of an implementation" means "I'm here and can do it quickly". |
| 23 |
|
| 24 |
-- |
| 25 |
|
| 26 |
Andreas K. Huettel |
| 27 |
Gentoo Linux developer |
| 28 |
dilfridge@g.o |
| 29 |
http://www.akhuettel.de/ |
Archives