From: Robert Pluim <rpluim@gmail.com>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: "Gregory Heytings" <gregory@heytings.org>,
"Michael Albinus" <michael.albinus@gmx.de>,
"Gerd Möllmann" <gerd.moellmann@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Emacs git repo mangled
Date: Wed, 02 Nov 2022 11:56:54 +0100 [thread overview]
Message-ID: <874jvhoc95.fsf@gmail.com> (raw)
In-Reply-To: <7be379b823dbdfe02ddf29c023b73d88@webmail.orcon.net.nz> (Phil Sainty's message of "Wed, 02 Nov 2022 15:11:06 +1300")
>>>>> On Wed, 02 Nov 2022 15:11:06 +1300, Phil Sainty <psainty@orcon.net.nz> said:
Phil> Client-side git hooks must be installed manually by the user (they
Phil> cannot be supplied automatically while cloning), so it would be up to
Phil> individuals to follow some documentation to do this; but the benefit
Phil> of a hook-based approach is that it should work regardless of how the
Phil> "git bisect start" is triggered (rather than relying on people using
Phil> the command line), which benefits people using Magit's bisect UI (to
Phil> pick an obvious example).
Thatʼs not an issue: autogen.sh currently installs some client-side
hooks already.
Robert
--
next prev parent reply other threads:[~2022-11-02 10:56 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 9:50 Emacs git repo mangled Michael Albinus
2022-10-31 13:09 ` Gerd Möllmann
2022-10-31 16:43 ` Michael Albinus
2022-11-01 5:44 ` Gerd Möllmann
2022-11-01 9:15 ` Michael Albinus
2022-11-01 9:28 ` Gerd Möllmann
2022-11-01 12:07 ` Gregory Heytings
2022-11-01 13:32 ` Michael Albinus
2022-11-01 13:55 ` Gregory Heytings
2022-11-01 15:23 ` Michael Albinus
2022-11-01 16:47 ` Gregory Heytings
2022-11-01 17:19 ` Eli Zaretskii
2022-11-01 18:25 ` Gregory Heytings
2022-11-02 5:51 ` Gerd Möllmann
2022-11-02 9:26 ` Gregory Heytings
2022-11-01 19:02 ` Michael Albinus
2022-11-01 19:41 ` Gregory Heytings
2022-11-02 3:26 ` Eli Zaretskii
2022-11-02 9:14 ` Gregory Heytings
2022-11-02 12:59 ` Phil Sainty
2022-11-02 13:10 ` Gregory Heytings
2022-11-02 13:49 ` Eli Zaretskii
2022-11-02 14:27 ` Gregory Heytings
2022-11-05 10:54 ` Michael Albinus
2022-11-05 21:58 ` Gregory Heytings
2022-11-02 2:11 ` Phil Sainty
2022-11-02 10:56 ` Robert Pluim [this message]
2022-10-31 13:38 ` Andreas Schwab
2022-10-31 16:45 ` Michael Albinus
2022-10-31 15:35 ` João Távora
2022-10-31 16:04 ` Stefan Kangas
2022-10-31 16:24 ` João Távora
2022-10-31 17:28 ` Stefan Kangas
2022-10-31 21:45 ` Gregory Heytings
-- strict thread matches above, loose matches on Subject: below --
2022-10-31 15:25 Payas Relekar
2022-10-31 16:11 ` João Távora
2022-10-31 16:48 ` Michael Albinus
2022-10-31 17:57 ` Stefan Monnier
2022-10-31 18:33 ` Andreas Schwab
2022-10-31 20:39 ` Stefan Monnier
2022-10-31 21:10 ` Óscar Fuentes
2022-10-31 21:15 ` Andreas Schwab
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=874jvhoc95.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=gregory@heytings.org \
--cc=michael.albinus@gmx.de \
--cc=psainty@orcon.net.nz \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.