From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Robin H. Johnson" <robbat2@gentoo.org>,
"Michał Górny" <mgorny@gentoo.org>,
"Git Mailing List" <git@vger.kernel.org>,
"Jeff King" <peff@peff.net>,
"Lars Schneider" <larsxschneider@gmail.com>
Subject: Re: [RFC PATCH] checkout: Force matching mtime between files
Date: Thu, 26 Apr 2018 19:53:58 +0200 [thread overview]
Message-ID: <20180426175358.15495-1-szeder.dev@gmail.com> (raw)
In-Reply-To: <20180426171540.GA2037@duynguyen.home>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1394 bytes --]
> On Wed, Apr 25, 2018 at 10:41:18AM +0200, Ævar Arnfjörð Bjarmason wrote:
> > 2. Add some config so we can have hook search paths, and ship with a
> > default search path for hooks shipped with git.
>
> I would go for something like this instead of search paths. This
> allows you to specify a path to any specific hook in hooks.* config
> group. This is basically "$GIT_DIR/hooks directory in config file" but
> with lower priority than those in $GIT_DIR/hooks.
>
> Now we can do something like
>
>
> git -c hooks.post-checkout=/path/to/some/script clone ...
>
> but of course I would need to fix the FIXME or this hook config is
> only effective just this one time. (And of course you could put it in
> ~/.gitconfig)
>
> -- 8< --
> diff --git a/builtin/clone.c b/builtin/clone.c
> index 7df5932b85..143413ed2d 100644
> --- a/builtin/clone.c
> +++ b/builtin/clone.c
> @@ -1063,6 +1063,11 @@ int cmd_clone(int argc, const char **argv, const char *prefix)
> strbuf_addf(&branch_top, "refs/remotes/%s/", option_origin);
> }
>
> + /*
> + * FIXME: we should keep all custom config settings via
> + * "git -c ..." in $GIT_DIR/config.
> + */
> +
We definitely should not, see the difference between 'git -c ... clone
url' and 'git clone -c ... url'
BTW, wouldn't running
git clone --template=/path/to/template/dir/with/hooks/
invoke the post-checkout hook in there?
next prev parent reply other threads:[~2018-04-26 17:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 17:01 [RFC PATCH] checkout: Force matching mtime between files Michał Górny
2018-04-23 20:07 ` Robin H. Johnson
2018-04-23 23:41 ` Junio C Hamano
2018-04-25 7:13 ` Robin H. Johnson
2018-04-25 8:48 ` Junio C Hamano
2018-04-25 15:18 ` Marc Branchaud
2018-04-25 20:07 ` Robin H. Johnson
2018-04-26 1:25 ` Junio C Hamano
2018-04-26 14:12 ` Marc Branchaud
2018-04-26 14:46 ` Michał Górny
2018-04-28 14:23 ` Duy Nguyen
2018-04-28 19:35 ` Michał Górny
2018-04-26 16:43 ` Duy Nguyen
2018-04-26 17:48 ` Robin H. Johnson
2018-04-26 18:44 ` Duy Nguyen
2018-04-29 23:56 ` Junio C Hamano
2018-04-30 15:10 ` Duy Nguyen
2018-04-27 17:03 ` Duy Nguyen
2018-04-27 21:08 ` Elijah Newren
2018-04-28 6:08 ` Duy Nguyen
2018-04-29 23:47 ` Junio C Hamano
2018-04-27 21:08 ` Marc Branchaud
2018-04-28 6:16 ` Duy Nguyen
2018-04-27 17:18 ` Michał Górny
2018-04-27 19:53 ` Ævar Arnfjörð Bjarmason
2018-04-25 8:41 ` Ævar Arnfjörð Bjarmason
2018-04-26 17:15 ` Duy Nguyen
2018-04-26 17:51 ` Robin H. Johnson
2018-04-26 17:53 ` SZEDER Gábor [this message]
2018-04-26 18:45 ` Duy Nguyen
2018-04-24 14:41 ` Marc Branchaud
2018-04-25 6:58 ` Robin H. Johnson
2018-04-25 7:13 ` Michał Górny
2018-05-05 18:44 ` Jeff King
2018-05-06 3:37 ` 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=20180426175358.15495-1-szeder.dev@gmail.com \
--to=szeder.dev@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
--cc=mgorny@gentoo.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=robbat2@gentoo.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).