From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: ChangeLog kde5.eclass
Date: Mon, 18 May 2015 09:47:33 +0200 [thread overview]
Message-ID: <20150518094733.4927fa85@gentoo.org> (raw)
In-Reply-To: <55587F5C.2060807@gentoo.org>
On Sun, 17 May 2015 13:45:32 +0200
hasufell <hasufell@gentoo.org> wrote:
> On 05/17/2015 10:16 AM, Jeroen Roovers wrote:
> > On Sun, 17 May 2015 06:08:56 +1000
> > Michael Palimaka <kensington@gentoo.org> wrote:
> >
> >>> 15 May 2015; Michael Palimaka <kensington@gentoo.org>
> >>> kde4-base.eclass: Sync with KDE overlay - update SRC_URI.
> >>>
> >>
> >> This is a complete description of the changes made.
> >
> > OK, then that dash should be interpreted as an em dash, I guess, and
> > "Sync with KDE overlay" is a development note intended for that
> > overlay (yeah, we downstreamed that!) that accidentally slipped
> > into the main tree, adding nothing useful.
> >
> >
> > jer
> >
>
> That is a limitation of CVS
Use mgorny's pull request framework if you can't properly use CVS.
Somehow it manages to get it right and also happens to commit to CVS...
> not being able to do actual merges. I'd
> say it's debatable whether "merge information" should be manually
> added to the ChangeLog entry. I think it can be left to the
> maintainer.
https://devmanual.gentoo.org/ebuild-writing/misc-files/changelog/index.html#writing-correct-changelog-messages
prev parent reply other threads:[~2015-05-18 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150509102236.DF9B09D3@oystercatcher.gentoo.org>
2015-05-10 4:44 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: ChangeLog kde5.eclass Michał Górny
2015-05-16 20:04 ` Jeroen Roovers
2015-05-16 20:08 ` Michael Palimaka
2015-05-17 8:16 ` Jeroen Roovers
2015-05-17 11:45 ` hasufell
2015-05-18 7:47 ` Alexis Ballier [this message]
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=20150518094733.4927fa85@gentoo.org \
--to=aballier@gentoo.org \
--cc=gentoo-dev@lists.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