From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: Raul E Rangel <rrangel@chromium.org>,
git@vger.kernel.org, Jeff King <peff@peff.net>,
demerphq <demerphq@gmail.com>
Subject: Re: [PATCH] archive: add --mtime
Date: Sat, 18 Feb 2023 09:25:04 -0800 [thread overview]
Message-ID: <xmqqilfykhsf.fsf@gitster.g> (raw)
In-Reply-To: <91a73f5d-ca3e-6cb0-4ba3-38d703074ee6@web.de> ("René Scharfe"'s message of "Sat, 18 Feb 2023 09:36:23 +0100")
René Scharfe <l.s.r@web.de> writes:
> +--mtime=<time>::
> + Set modification time of archive entries. Without this option
> + the committer time is used if `<tree-ish>` is a commit or tag,
> + and the current time if it is a tree.
> +
> <extra>::
> This can be any options that the archiver backend understands.
> See next section.
> diff --git a/archive.c b/archive.c
> index 81ff76fce9..122860b39d 100644
> --- a/archive.c
> +++ b/archive.c
> @@ -472,6 +472,8 @@ static void parse_treeish_arg(const char **argv,
> commit_oid = NULL;
> archive_time = time(NULL);
> }
> + if (ar_args->mtime_option)
> + archive_time = approxidate(ar_args->mtime_option);
This is the solution with least damage, letting the existing code to
set archive_time and then discard the result and overwrite with the
command line option.
I wonder if we want to use approxidate_careful() to deal with bogus
input? The code is perfectly serviceable without it (users who feed
bogus input deserve what they get), but some folks might prefer to
be "nicer" than necessary ;-)
Other than that, looks very good. Thanks.
next prev parent reply other threads:[~2023-02-18 17:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 19:41 Feature request: Add --mtime option to git archive Raul E Rangel
2023-02-16 21:05 ` Jeff King
2023-02-16 22:21 ` Junio C Hamano
2023-02-17 0:50 ` Jeff King
2023-02-17 2:04 ` Junio C Hamano
2023-02-17 15:43 ` Raul Rangel
2023-02-17 20:31 ` René Scharfe
2023-02-17 20:25 ` Jeff King
2023-02-18 3:04 ` demerphq
2023-02-18 17:08 ` brian m. carlson
2023-02-18 8:36 ` [PATCH] archive: add --mtime René Scharfe
2023-02-18 17:25 ` Junio C Hamano [this message]
2023-02-19 10:44 ` René Scharfe
2023-02-21 5:37 ` Junio C Hamano
2023-02-22 19:51 ` Jeff King
2023-02-22 23:23 ` 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=xmqqilfykhsf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=demerphq@gmail.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=peff@peff.net \
--cc=rrangel@chromium.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.