Dnia 2 listopada 2015 06:50:39 CET, "Robin H. Johnson" <robb...@gentoo.org> napisał(a): >I'm replying to the top level of the thread, because I've been on >offline vacation recharging myself for a week, and this thread seems to >have degenerated into ways to avoid the issue, rather than focusing >with >what's actually wrong. > >rsync-as-a-way-to-get-the-tree is NOT being deprecated, it has very >valid use cases, and places where git is not suited. > >I asked zmedico & dol-sen for TWO critical changes to egencache's >--update-changelogs code. > >1. Control of the OUTPUT filename for the generated changelog >- the from-git generated changelog will go to 'ChangeLog.git' >2. Control for the order ENTRY for the generated changelog >- changing to OLDEST-first, with appending the new data at the end >- this massively improves rsync performance. > >dol-sen said he was busy with the repoman rewrite, and didn't want to >introduce the change at the time, so this has been deferred for the >moment. > >Without #1, we have to rename ALL of the old changelogs, otherwise they >will be overwritten by the new ones from Git history. > >I probably should have created a bug for both of these, because I don't >know if they got tracked accurately since I asked for them in August, >and I certainly don't see the code being updated in the repoman or >master branches of the portage repo (it also still generates a $Header$ >entry, which does have an open bug as we.
You should have indeed. Both seem trivial and I'd have done them a long time ago if anybody bothered telling me about it. > >Since dol-sen and zmedico are so busy as well, somebody from this >thread >with time to complain, please implement & test these changes! >It's NOT as trivial as dropping a variable into the place where it >opens >the file, because there is other code later that also hardcodes the >filename. -- Best regards, Michał Górny
