git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Jesús Ariel Cabello Mateos" <080ariel@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: rss/atom change published/updated date to committed date
Date: Fri, 05 Jul 2024 23:08:26 -0700	[thread overview]
Message-ID: <xmqq7cdz3vdx.fsf@gitster.g> (raw)
In-Reply-To: <20240704164547.94341-1-080ariel@gmail.com> ("Jesús Ariel Cabello Mateos"'s message of "Thu, 4 Jul 2024 16:45:35 +0000")

Jesús Ariel Cabello Mateos <080ariel@gmail.com> writes:

> Currently the published(in rss) and the updated(in atom) date
> used is the authored date. Change it to the committed date 
> that betters reflect the "published/updated" definition and 
> makes rss/atom feeds more lineal. Gitlab/Github rss/atom feeds 
> use the commited date.
>
> The committed date is already used to determine if more items
> should be fetched.

Even though "authored" and "committed" date may be grammatically
correct if you use "to author" and "to commit" as verbs, the name we
use for these two timestamps are "author date" and "committer date"
(in other words, "author" and "committer" are not used as verbs but
as nouns for possibly two distinct people).  So

 * "committed date" (on the title and elsewhere) and "commited date"
   -> "committer date".

 * "authored date" -> "author date".

 * "lineal" -> "linear"?

But your reasoning is absolutely correct about the concept of
"publish" more closely corresponds to the committer date than the
author date, and the change looks sensible.

> Signed-off-by: Jesús Ariel Cabello Mateos <080ariel@gmail.com>
> ---
>  gitweb/gitweb.perl | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> index ccd14e0e30..0ef5707557 100755
> --- a/gitweb/gitweb.perl
> +++ b/gitweb/gitweb.perl
> @@ -8329,7 +8329,7 @@ sub git_feed {
>  		if (($i >= 20) && ((time - $co{'author_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,

  reply	other threads:[~2024-07-06  6:08 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 [this message]
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
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=xmqq7cdz3vdx.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 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).