From: "Thompson, David" <dthompson2@worcester.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 56444@debbugs.gnu.org, 56444-done@debbugs.gnu.org,
Maxime Devos <maximedevos@telenet.be>
Subject: bug#56444: [EXT] Re: bug#56444: Gitolite home directory permissions
Date: Tue, 30 Aug 2022 12:39:47 -0400 [thread overview]
Message-ID: <CAJ=Rwfa4Yskk=gzV2HepozfKWRBCE9MVzhhOwVqZ3NrEqFm+Fw@mail.gmail.com> (raw)
In-Reply-To: <87edwxwyf9.fsf_-_@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Hi Ludo,
On Tue, Aug 30, 2022 at 11:20 AM Ludovic Courtès <ludo@gnu.org> wrote:
> Hi there!
>
> Please let’s avoid guessing each other’s willingness to do one thing or
> another.
>
> I agree with David that we should accept simple local fixes like this
> one, while keeping the “better solution” in sight. It’s a tradeoff, and
> the goal is to make sure we can all move forward.
>
> So I’m all for merging this Gitolite activation patch that David posted
> right away; I think you can go ahead, David.
>
> Adding ‘home-permission’ to <user-account> as Maxime suggested also
> sounds like a welcome improvement to me, but I think it’s fine to do
> that separately.
>
Patch pushed.
I will follow up with a new bug report (and a patch later when I have some
time to actually write code) to capture the improvements to <user-account>
so we can discuss any potential issues or gotchas that might come as a
result.
Thanks,
- Dave
[-- Attachment #2: Type: text/html, Size: 1409 bytes --]
next prev parent reply other threads:[~2022-08-30 16:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 21:35 bug#56444: Gitolite home directory permissions Evgeny Pisemsky
[not found] ` <handler.56444.B.165722972531874.ack@debbugs.gnu.org>
2022-07-08 8:10 ` bug#56444: Acknowledgement (Gitolite home directory permissions) Evgeny Pisemsky
2022-08-19 13:32 ` bug#56444: Patch to fix Gitolite home directory permissions Thompson, David
2022-08-23 12:41 ` Maxime Devos
2022-08-23 14:45 ` Thompson, David
2022-08-29 12:49 ` Thompson, David
2022-08-29 12:52 ` Maxime Devos
2022-08-29 12:57 ` bug#56444: [EXT] " Thompson, David
2022-08-29 13:09 ` Maxime Devos
2022-08-29 13:11 ` Maxime Devos
2022-08-29 13:19 ` Maxime Devos
2022-08-29 13:30 ` bug#56444: [EXT] " Thompson, David
2022-08-29 13:44 ` Maxime Devos
2022-08-29 13:59 ` bug#56444: [EXT] " Thompson, David
2022-08-29 21:05 ` zimoun
2022-08-30 15:20 ` bug#56444: " Ludovic Courtès
2022-08-30 16:39 ` Thompson, David [this message]
2022-08-30 18:31 ` david larsson
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ=Rwfa4Yskk=gzV2HepozfKWRBCE9MVzhhOwVqZ3NrEqFm+Fw@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=56444-done@debbugs.gnu.org \
--cc=56444@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
/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://git.savannah.gnu.org/cgit/guix.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).