From: Joel Brobecker <brobecker@adacore.com>
To: overseers@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: transition git-hooks on sourceware.org to Python 3.x
Date: Fri, 17 Dec 2021 06:46:50 +0400 [thread overview]
Message-ID: <Ybv6GmaM/UKstg1j@adacore.com> (raw)
In-Reply-To: <YbXd30MXu7ZMNXVC@adacore.com>
Hello,
> I've created a small prototype and did some testing with it,
> it seems to work well. In a nutshell, we have:
>
> <wrappers root>/
> - hooks/ <-- directory to use as hooks in Git bare repos
> - git-hooks/ <-- clone of https://github.com/adacore/git-hooks
> - python3-for-git-hooks/ <-- Python 3.x venv to be used by the git-hooks
>
> To transition a repository to updated hooks, we simply replace
> the hooks symbolic link to point to <wrappers root>/hooks.
>
> My proptotype is at...
>
> /home/gdbadmin/brobecke/py3-git-hooks/git-hooks-wrapper
>
> ... for those who are curious and can log onto sourceware.org.
> There is a README.md file that gives a bit more information
> (I'll attach to this message as well)
>
> If agreed with the approach, I think we'll want to decide where
> we want this to live. Maybe /sourceware/projects/src-home/?
If there are no opinions, I'll use gdbadmin's home. I don't think
this is the ideal location, but that's one where I currently have
access to.
> The main issue with this location is that I worry about shared
> access and in particular maintenance over time. I'd like to be
> able to make changes there if there is a need to fix something.
> I'd like also to be able to continue updating the git-hooks version
> being used as I continue to push fixes and enhancements.
Thank you,
--
Joel
next prev parent reply other threads:[~2021-12-17 2:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 11:32 Joel Brobecker
2021-12-13 9:23 ` Mark Wielaard
2021-12-15 9:30 ` Ivo Raisr
2021-12-16 2:16 ` Joel Brobecker
2021-12-13 11:35 ` Corinna Vinschen
2021-12-13 11:47 ` Joel Brobecker
2021-12-13 22:20 ` Joseph Myers
2021-12-14 3:39 ` Joel Brobecker
2021-12-17 2:46 ` Joel Brobecker [this message]
2021-12-19 4:45 ` Joel Brobecker
2021-12-20 5:10 ` Joel Brobecker
2022-01-16 10:06 ` Joel Brobecker
2022-01-17 10:02 ` Corinna Vinschen
2022-01-20 5:27 ` Joel Brobecker
2022-01-20 10:04 ` Corinna Vinschen
2022-01-20 13:54 ` Joel Brobecker
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=Ybv6GmaM/UKstg1j@adacore.com \
--to=brobecker@adacore.com \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).