From: Nicolas Bock <nicolasbock@gentoo.org>
To: Marius Brehler <marbre@linux.sungazer.de>
Cc: Nicolas Bock <nicolasbock@gentoo.org>,
sci@gentoo.org,
Gentoo Science List <gentoo-science@lists.gentoo.org>
Subject: [gentoo-science] Re: ChangeLog in the overlay
Date: Tue, 13 Oct 2015 14:50:23 -0600 [thread overview]
Message-ID: <CAPMKG4Dzcvs7YsTH9muaJO-13jA8xTFD+tSrwvYnEeSBqdfRkg@mail.gmail.com> (raw)
In-Reply-To: <561D6C9E.5080403@linux.sungazer.de>
On Tue, Oct 13, 2015 at 2:42 PM, Marius Brehler
<marbre@linux.sungazer.de> wrote:
> On 10/13/2015 02:08 PM, Nicolas Bock wrote:
>> On Mon, Oct 12, 2015 at 4:58 AM, Marius Brehler
>> <marbre@linux.sungazer.de> 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
next prev parent reply other threads:[~2015-10-13 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 10:35 [gentoo-science] ChangeLog in the overlay Justin Lecher (jlec)
2015-10-10 10:42 ` François Bissey
2015-10-10 13:38 ` Justin Lecher (jlec)
2015-10-10 22:20 ` Olivier Huber
2015-10-13 20:55 ` François Bissey
[not found] ` <561B9252.5080401@linux.sungazer.de>
2015-10-13 12:08 ` [gentoo-science] " Nicolas Bock
[not found] ` <561D6C9E.5080403@linux.sungazer.de>
2015-10-13 20:50 ` Nicolas Bock [this message]
[not found] ` <561DF32B.8060406@linux.sungazer.de>
2015-10-14 11:50 ` Nicolas Bock
2016-01-07 14:13 ` [gentoo-science] " Justin Lecher (jlec)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPMKG4Dzcvs7YsTH9muaJO-13jA8xTFD+tSrwvYnEeSBqdfRkg@mail.gmail.com \
--to=nicolasbock@gentoo.org \
--cc=gentoo-science@lists.gentoo.org \
--cc=marbre@linux.sungazer.de \
--cc=sci@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox