From: Chinmoy Chakraborty <chinmoy12c@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: updated documentation for git commit --date
Date: Mon, 29 Mar 2021 11:32:38 +0530 [thread overview]
Message-ID: <98c196c4-31ff-4df1-9215-77d115771583@gmail.com> (raw)
In-Reply-To: <6a9d24a9-6942-97fc-550f-6b9b61264a78@gmail.com>
On 3/29/21 10:55 AM, Bagas Sanjaya wrote:
> Is date format parsing specific to git commit? If so, then
> why not date-formats.txt be merged to `DATE FORMATS` section
> of git-commit documentation?
It is already included below the `COMMIT INFORMATION` section.
> Also, what commit this `--date`
> option first appeared before you write this documentation?
I guess it was introduced in commit
a8aca418d6484400d6804e22717bd49ca06c28e9.
>
>> +`tea`::
>> + Change commit time to 17:00(tea time). If the current
>> + time is less than 17:00, the time will be set to 17:00
>> + on the previous day, else it will be set to 17:00 on
>> + the same day.
> How useful is this argument?
>
I think initially it was suggested as a joke, but actually implemented
to demonstrate the ability for users to include their own custom
time/date periods.
See :
https://github.com/git/git/commit/a8aca418d6484400d6804e22717bd49ca06c28e9
next prev parent reply other threads:[~2021-03-29 6:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 10:19 [PATCH] Documentation: updated documentation for git commit --date Chinmoy via GitGitGadget
2021-03-28 12:54 ` [PATCH v2] " Chinmoy via GitGitGadget
2021-03-29 5:25 ` Bagas Sanjaya
2021-03-29 6:02 ` Chinmoy Chakraborty [this message]
2021-03-29 11:11 ` Bagas Sanjaya
2021-03-29 14:56 ` Chinmoy Chakraborty
2021-03-29 21:27 ` Junio C Hamano
2021-03-30 16:38 ` Chinmoy Chakraborty
2021-03-30 17:28 ` 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
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=98c196c4-31ff-4df1-9215-77d115771583@gmail.com \
--to=chinmoy12c@gmail.com \
--cc=bagasdotme@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.
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).