From: Junio C Hamano <gitster@pobox.com>
To: Ariel Cabello Mateos <080ariel@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] gitweb: rss/atom change published/updated date to committer date
Date: Sat, 06 Jul 2024 15:35:49 -0700 [thread overview]
Message-ID: <xmqqle2em9mi.fsf@gitster.g> (raw)
In-Reply-To: <xmqq8qyenpsz.fsf@gitster.g> (Junio C. Hamano's message of "Sat, 06 Jul 2024 15:01:00 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Ariel Cabello Mateos <080ariel@gmail.com> writes:
>
>> Currently the value used is the author date. Change it to the
It is left unsaid what "the value" is used for. Let's rewrite the
first sentence like so:
The author date is used for published/updated date in the
rss/atom feed stream. Change it to ...
Another thing that is curious is why the mention of author_epoch is
left as is before the hunk.
Shouldn't we use the same committer time for loop cut-off and also
for display?
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index e66eb3d9ba..c1151544cc 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -8324,10 +8324,10 @@ sub git_feed {
my %co = %{$commitlist[$i]};
my $commit = $co{'id'};
# we read 150, we always show 30 and the ones more recent than 48 hours
- if (($i >= 20) && ((time - $co{'author_epoch'}) > 48*60*60)) {
+ if (($i >= 20) && ((time - $co{'committer_epoch'}) > 48*60*60)) {
last;
}
- my %cd = parse_date($co{'author_epoch'}, $co{'author_tz'});
+ my %cd = parse_date($co{'committer_epoch'}, $co{'committer_tz'});
# get list of changed files
open my $fd, "-|", git_cmd(), "diff-tree", '-r', @diff_opts,
--
2.45.2-899-gfb4fe62777
next prev parent reply other threads:[~2024-07-06 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 16:45 [PATCH] gitweb: rss/atom change published/updated date to committed date Jesús Ariel Cabello Mateos
2024-07-06 6:08 ` Junio C Hamano
2024-07-06 16:16 ` [PATCH v2] gitweb: rss/atom change published/updated date to committer date Ariel Cabello Mateos
2024-07-06 22:01 ` Junio C Hamano
2024-07-06 22:35 ` Junio C Hamano [this message]
2024-07-07 18:48 ` [PATCH v3] " Jesús Ariel Cabello Mateos
2024-07-08 11:11 ` Junio C Hamano
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=xmqqle2em9mi.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=080ariel@gmail.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.