On Tue, Oct 13, 2015 at 2:42 PM, Marius Brehler <[email protected]> wrote: > On 10/13/2015 02:08 PM, Nicolas Bock wrote: >> On Mon, Oct 12, 2015 at 4:58 AM, Marius Brehler >> <[email protected]> wrote: >>> >>> >>> On 10/10/2015 12:35 PM, Justin Lecher (jlec) wrote: >>>> Hi everyone, >>>> >>>> What is your opinion on dropping the ChangeLog in the overlay in >>>> favour of the git log as it has been done in the tree? >>>> >>>> Justin >>>> >>> >>> Hi, >>> I prefer to drop the ChangeLogs. Since we give a lot advices and many >>> contributes push their changes incremental without using 'repo-commit >>> -t', or re-commit changed ebuilds, ChangeLogs often blow up. For example >>> see [1], which is AFAIR not the worst one. >>> Regards >>> >> Hi Marius, >> >> out of curiosity: What does the -t option do? And how does one >> re-commit a change using repoman? >> >> Thanks, >> >> Nick > > > Hi, > the -t option prevents adding a ChangeLog entry: > > -t, --trivial trivial changes (do not add a ChangeLog entry) > > > With re-commiting, I mean one could reset without loosing the > modifications with 'git reset --soft HEAD^' (or by specifying a commit > hash/tag/e.g.), apply the new changes/caring for the annotations and > than just executing 'repo-commit <previous commit message>' again. > I hope that answers your question, if not please let me know. > Regards > Thanks, that explains it! I missed that you are using 'repo-commit' and not 'repoman' :) Is repo-commit recommended over repoman?
> Marius
