git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "blanet via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  blanet <bupt_xingxin@163.com>,
	 Xing Xin <xingxin.xx@bytedance.com>
Subject: Re: [PATCH] Documentation: fix typos describing date format
Date: Fri, 12 Apr 2024 09:02:41 -0700	[thread overview]
Message-ID: <xmqqh6g6po0u.fsf@gitster.g> (raw)
In-Reply-To: <pull.1716.git.1712911876943.gitgitgadget@gmail.com> (blanet via GitGitGadget's message of "Fri, 12 Apr 2024 08:51:16 +0000")

"blanet via GitGitGadget" <gitgitgadget@gmail.com> writes:

> From: Xing Xin <xingxin.xx@bytedance.com>
>
> This commit corrects a typographical error found in both
> date-formats.txt and git-fast-import.txt documentation, where the term
> `email format` was mistakenly used instead of `date format`.

Saying "date" is much more correct than "email" ;-).  Thanks for
noticing both instances.

>  Documentation/date-formats.txt    | 2 +-
>  Documentation/git-fast-import.txt | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/date-formats.txt b/Documentation/date-formats.txt
> index 67645cae64f..e24517c496f 100644
> --- a/Documentation/date-formats.txt
> +++ b/Documentation/date-formats.txt
> @@ -11,7 +11,7 @@ Git internal format::
>  	For example CET (which is 1 hour ahead of UTC) is `+0100`.
>  
>  RFC 2822::
> -	The standard email format as described by RFC 2822, for example
> +	The standard date format as described by RFC 2822, for example
>  	`Thu, 07 Apr 2005 22:13:13 +0200`.

RFC 2822 defines it as "date-time" (and this hasn't been updated by
RFC 5322).  "date" is used to specifically mean "day month year".

    https://www.rfc-editor.org/rfc/rfc2822.html#section-3.3

    date-time       =       [ day-of-week "," ] date FWS time [CFWS]
    day-of-week     =       ([FWS] day-name) / obs-day-of-week
    day-name        =       "Mon" / "Tue" / "Wed" / "Thu" /
                            "Fri" / "Sat" / "Sun"
    date            =       day month year

So the new phrasing may get complain from pedants.  Saying "The
standard date-time format as described by RFC 2822" is more
technically correct, but I actually wonder if we should go in the
opposite, looser direction, like

	The timestamp format used by RFC 2822, for example
	...

so that we do not even pretend to use the wording they use in the
RFC documents.  Doing so makes it in line with "git rev-list --help"
which says

	"--date=rfc" shows timestamps in RFC 2822 format, often
        found in e-mail messages.

But that's minor.  "date" is fine as-is.  The same comment applies
to the other hunk.

Thanks.

> diff --git a/Documentation/git-fast-import.txt b/Documentation/git-fast-import.txt
> index b2607366b91..0ccede255ea 100644
> --- a/Documentation/git-fast-import.txt
> +++ b/Documentation/git-fast-import.txt
> @@ -303,7 +303,7 @@ and some sanity checks on the numeric values may also be performed.
>  	with e.g. bogus timezone values.
>  
>  `rfc2822`::
> -	This is the standard email format as described by RFC 2822.
> +	This is the standard date format as described by RFC 2822.
>  +
>  An example value is ``Tue Feb 6 11:22:18 2007 -0500''.  The Git
>  parser is accurate, but a little on the lenient side.  It is the
>
> base-commit: 436d4e5b14df49870a897f64fe92c0ddc7017e4c


      reply	other threads:[~2024-04-12 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12  8:51 [PATCH] Documentation: fix typos describing date format blanet via GitGitGadget
2024-04-12 16:02 ` Junio C Hamano [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqh6g6po0u.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=bupt_xingxin@163.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=xingxin.xx@bytedance.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).