From: David Thompson <dthompson2@worcester.edu>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add gitolite.
Date: Fri, 24 Apr 2015 10:05:58 -0400 [thread overview]
Message-ID: <87zj5x8vuh.fsf@fsf.org> (raw)
In-Reply-To: <idj618qyg4e.fsf@bimsb-sys02.mdc-berlin.net>
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
> David Thompson writes:
>
>> David Thompson <dthompson2@worcester.edu> writes:
>>
>>> Gitolite is a lightweight tool for managing access control to Git
>>> repositories. We use it at the FSF and it works pretty well.
>>>
>>> AFAICT, I've managed to avoid propogating Perl, but I have to propagate
>>> OpenSSH and Git for now. They are referenced in too many scripts in too
>>> many ways for a regexp substitution to do a good job. Fixing this
>>> requires working with the upstream maintainers, I think.
>>>
>>> From 12a8ab427800a004059c847742fa40bf35de1bb2 Mon Sep 17 00:00:00 2001
>>> From: David Thompson <davet@gnu.org>
>>> Date: Thu, 16 Apr 2015 03:23:52 -0400
>>> Subject: [PATCH] gnu: Add gitolite.
>>
>> I would like to push this soon if there are no objections.
>
> I just went over the patch set and it looks good to me.
>
> Pity about OpenSSH and Git being propagated, but I agree that this
> should be a task for upstream (e.g. allowing to pass paths to both tools
> with configure flags or so).
Thanks for taking a look. I cleaned the patch up a bit, added a couple
more comments, and pushed.
--
David Thompson
Web Developer - Free Software Foundation - http://fsf.org
GPG Key: 0FF1D807
Support the FSF: https://fsf.org/donate
prev parent reply other threads:[~2015-04-24 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 11:36 [PATCH] gnu: Add gitolite David Thompson
2015-04-20 15:16 ` David Thompson
2015-04-20 15:27 ` Ricardo Wurmus
2015-04-24 14:05 ` David Thompson [this message]
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=87zj5x8vuh.fsf@fsf.org \
--to=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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/guix.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.