On Wed, Nov 2, 2016 at 2:39 PM, Brent W. Baccala
wrote:
> On Wed, Nov 2, 2016 at 2:26 PM, Kalle Olavi Niemitalo wrote:
>
>>
>> Look at how the commit messages in hurd.git at Savannah (not at
>> Debian) are formatted. "make dist" runs gitlog-to-changelog,
>> which generates a ChangeLog file from
On Wed, Nov 2, 2016 at 2:26 PM, Kalle Olavi Niemitalo wrote:
>
> Look at how the commit messages in hurd.git at Savannah (not at
> Debian) are formatted. "make dist" runs gitlog-to-changelog,
> which generates a ChangeLog file from those.
>
OK, I think I see what you want.
"Brent W. Baccala" writes:
> How do you submit changelog-style descriptions? They don't seem to be kept
> in ChangeLog...
Look at how the commit messages in hurd.git at Savannah (not at
Debian) are formatted. "make dist" runs gitlog-to-changelog,
which generates a ChangeLog file from those.
(
On Wed, Nov 2, 2016 at 3:10 AM, Justus Winter wrote:
>
> Cool. Two nitpicks: 1/ Instead of attaching patches, why don't you use
> git send-email. That is easier for everyone. 2/ The summary line of
> your patches is too long, try to keep it at ~60 chars or so, and we
> require changelog-style
Hi!
"Brent W. Baccala" writes:
> I'm attaching two more patches to rpctrace that close bug 48863.
Cool. Two nitpicks: 1/ Instead of attaching patches, why don't you use
git send-email. That is easier for everyone. 2/ The summary line of
your patches is too long, try to keep it at ~60 chars o
