| 1 |
On Thu, 12 Nov 2015 12:12:28 +0100 |
| 2 |
Ulrich Mueller <ulm@g.o> wrote: |
| 3 |
|
| 4 |
> >>>>> On Thu, 12 Nov 2015, Jason Zaman wrote: |
| 5 |
> |
| 6 |
> > On Thu, Nov 12, 2015 at 11:46:19AM +0100, Alexis Ballier wrote: |
| 7 |
> >> How should one report bugs ? to infra or portage ? |
| 8 |
> >> From my just rsynced tree, I see changelogs in reverse order: oldest |
| 9 |
> >> come first, latest come last |
| 10 |
> |
| 11 |
> > NOTABUG, it was changed because rsync can deal really well with |
| 12 |
> > appending to the end of files. rsyncing a file where things were |
| 13 |
> > things were added to the beginning of the file means rsync will copy |
| 14 |
> > the whole file from scratch which is pretty sub-optimal. |
| 15 |
> |
| 16 |
> Our ChangeLogs were always in newest-first order, so why would this |
| 17 |
> suddenly be an issue? |
| 18 |
> |
| 19 |
> Also readability for users should take priority over technical |
| 20 |
> matters. Newest first is the usual order (e.g. it agrees with the |
| 21 |
> default of git log), and ChangeLog having different order from |
| 22 |
> ChangeLog-20* seems rather confusing to me. |
| 23 |
|
| 24 |
I imagine it breaks emerge --changelog output as well? |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Ryan Hill psn: dirtyepic_sk |
| 29 |
gcc-porting/toolchain/wxwidgets @ gentoo.org |
| 30 |
|
| 31 |
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 |
Archives