[blfs-dev] Git server instructions

Armin K. krejzi at email.com
Wed Mar 5 06:41:00 PST 2014

On 03/05/2014 03:15 PM, akhiezer wrote:
>> Date: Wed, 05 Mar 2014 04:40:07 +0100
>> From: "Armin K." <krejzi at email.com>
>> To: BLFS Development List <blfs-dev at linuxfromscratch.org>
>> Subject: [blfs-dev] Git server instructions
>> Hello, I've taken some time to write some basic instructions on how to
>> get a basic git server up and running.
>> The instructions can be found at:
>> http://www.linuxfromscratch.org/~krejzi/blfs-git/general/gitserver.html
>> Patch against latest blfs svn can be found at:
>> http://www.linuxfromscratch.org/~krejzi/git-server.patch
>> Any comments and suggestions are welcome.
> The three off-site docs that you link to, are already showing the
> usual signs of 'chopping'n'changing version'-itis: in your doc, the
> 'Adding and removing users' and 'Adding and removing repositories'
> link to gitolite v3 docs ('http://gitolite.com/gitolite/users.html' &
> 'http://gitolite.com/gitolite/repos.html' resp), whereas the link 'modify the
> gitolite.conf filename as explained in [...] [url]this[/url] document' gives
> a v2 page ('http://gitolite.com/gitolite/g2/confother_.html'), that says at
> its top, "WARNING: This is not the latest gitolite; please see the README" .

Oops, my bad.

Unfortunately, I can't find the same page online for v3 (but this also
works for me).

There's an entry in README.txt though, but I see no clean way of
pointing user to it.

> That's the kind of thing that happens when working with not a fixed
> tarball/git-tag target, and instead using a moving target; ref preceding
> email re tarball &c.
> Overall, ideally if possible give example code for how the user would
> walkthrough setup of a simple config; and refer the user to the gitolite
> tarball infos &/or off-site docs for fuller details, in the usual way.
> And, of course, I'd really recommend nailing down a fixed gitolite version
> and using that.

Thanks for the input.

Note: My last name is not Krejzi.

More information about the blfs-dev mailing list