From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Chinmoy Chakraborty <chinmoy12c@gmail.com>, git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2] Documentation: updated documentation for git commit --date
Date: Mon, 29 Mar 2021 18:11:25 +0700 [thread overview]
Message-ID: <5f69547a-723c-05d4-e00c-c7a5d6760315@gmail.com> (raw)
In-Reply-To: <98c196c4-31ff-4df1-9215-77d115771583@gmail.com>
On 29/03/21 13.02, Chinmoy Chakraborty wrote:
> 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.
>
Hmmm...
The commit you mentioned (a8aca418d6484400d6804e22717bd49ca06c28e9)
said that:
> Thanks for pointing out tea-time.
>
> This is also written to easily extended to allow people to add their own
> important dates like Christmas and their own birthdays.
>
But it seems like the predefined dates/times were hard-coded, so to extend
--date option to allow more predefined date/times, Git sources need to
be edited.
Maybe we can make git config option (commit.predefined_times [FIXME: suggest
better name]) so user can easily add ones.
Also, I asked to you: can I set --date to arbitrary date (like 09/29/2009
19:59)?
[CC] Junio, what about this patch?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-03-29 11:12 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
2021-03-29 11:11 ` Bagas Sanjaya [this message]
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=5f69547a-723c-05d4-e00c-c7a5d6760315@gmail.com \
--to=bagasdotme@gmail.com \
--cc=chinmoy12c@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).