From: Michael J Gruber <git@drmicha.warpmail.net>
To: Remi Galan Alfonso <remi.galan-alfonso@ensimag.grenoble-inp.fr>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] git.spec: fix changelog dates
Date: Tue, 5 Apr 2016 15:41:24 +0200 [thread overview]
Message-ID: <5703C084.1040405@drmicha.warpmail.net> (raw)
In-Reply-To: <833355852.2977267.1459859316816.JavaMail.zimbra@ensimag.grenoble-inp.fr>
Remi Galan Alfonso venit, vidit, dixit 05.04.2016 14:28:
> Michael J Gruber <git@drmicha.warpmail.net> wrote:
>> A few changelog entries have inconsistent dates, which rpmlint reports
>> as errors.
>>
>> Fix them based on these assumptions:
>> - It's easier to mistype a number than a weekday abbreviation.
>> - changelog date must be before git commit date
>> - The mistyped date is just a few days off.
>>
>> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
>> ---
>> I dunno if this is worthwhile, but rpmlint is the first thing we tell
>> packagers and reviewers to check.
>>
>> git.spec.in | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/git.spec.in b/git.spec.in
>> index bfd1cfb..eb581a3 100644
>> --- a/git.spec.in
>> +++ b/git.spec.in
>> @@ -229,7 +229,7 @@ rm -rf $RPM_BUILD_ROOT
>> * Sat Jan 30 2010 Junio C Hamano <gitster@pobox.com>
>> - We don't ship Python bits until a real foreign scm interface comes.
>>
>> -* Mon Feb 04 2009 David J. Mellor <dmellor@whistlingcat.com>
>> +* Mon Feb 02 2009 David J. Mellor <dmellor@whistlingcat.com>
>> - fixed broken git help -w after renaming the git-core package to git.
>>
>> * Fri Sep 12 2008 Quy Tonthat <qtonthat@gmail.com>
>> @@ -262,7 +262,7 @@ rm -rf $RPM_BUILD_ROOT
>> * Thu Jun 21 2007 Shawn O. Pearce <spearce@spearce.org>
>> - Added documentation files for git-gui
>>
>> -* Tue May 13 2007 Quy Tonthat <qtonthat@gmail.com>
>> +* Sun May 13 2007 Quy Tonthat <qtonthat@gmail.com>
>
> It is inconsistent with what you said in the commit message ("It's
> easier to mistype a number than a weekday abbreviation.").
>
> Following that logic, it should be:
> * Tue May 15 2007 Quy Tonthat <qtonthat@gmail.com>
>
> (or 08, I didn't check the condition "changelog date must be before
> git commit date")
I did.
The thing is that you can't always fulfill all of these 3 conditions.
"Easier" doesn't mean that the other case is impossible, just less likely.
> Thanks,
> Rémi
>
next prev parent reply other threads:[~2016-04-05 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 12:09 [RFC/PATCH] git.spec: fix changelog dates Michael J Gruber
2016-04-05 12:28 ` Remi Galan Alfonso
2016-04-05 13:41 ` Michael J Gruber [this message]
2016-04-05 14:17 ` Remi Galan Alfonso
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=5703C084.1040405@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=remi.galan-alfonso@ensimag.grenoble-inp.fr \
/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;
as well as URLs for NNTP newsgroup(s).