gitolite-announce

Hi all Finally got done pushing out the patch that detects the HEAD branch's name in the gitolite

Hello all I pushed out v3.6.13 earlier this weekend. Compared to v3.6.12 there's only one "

Hi all, I've just pushed out a change to the mirroring code and documentation: "slave"/

Hello everyone, Nick Cleaton (ni...@cleaton.net) found and reported a security issue caused by

Hi all, dc13dfc (contained in 3.6.9) introduced a block on accessing repos which are in the process

In hindsight, saying things like "does not impact anything else" in the commit message for

Hi all Björn Kautler found a problem in the documented method to migrate existing repos to gitolite.

There's nothing major that people MUST have in this release (unless you're running kernel.org

Over the last few weeks, spurred on by Fedora having 42000+ repos and seeing some serious slowdowns

Hi everyone, I just pushed 3.6.7. I'm not sure if I've announced minor releases before, but

Hi all, Now you can test gitolite.conf access rules **on the client** before you push them out to the

Hi all Apologies to those who've already received this from other sources. The Git User's

On 09/08/2016 06:29 AM, Sitaram Chamarty wrote: > Hi > > I decided to send this mail when I

It should be working now; sorry about that (though if this should ever happen, that clone method will

V3.6.4 has been pushed. It isn't a very remarkable set of patches, but there is one interesting

Hi all, I just pushed v3.6.3. The CHANGELOG contains a summary at the top; see https://github.com/

Git 2.2 onwards has a "--signed" option to the push command. With inputs and ideas from

Hi, Someone pointed me to an issue with symbolic-ref, and I not only did not do anything about it,

Hi all, Several URLs exist, here's one: https://access.redhat.com/security/cve/CVE-2014-6271 To

Hi all, It seems that, sometime after I wrote gitolite's 'htpasswd' command, the real

Someone on IRC wanted a way to mirror gitolite to S3 using jgit, and to restore from that mirror to a

Hi, Back in March 2013 when v3.4 came out, the rc file format changed significantly, to make it

If you have these lines uncommented in your rc file: (in the "rc variables used by various

Hi all, Gitolite now has optional Redis caching in the "master" branch, and the old "

Amendment, now that v3.6 has been released. You don't need to add anything to the rc file; I

Hi all, I just pushed v3.6. (And Milki, I remembered to push the tag too!) It contains a few

I found the mail that led to this, see [1]. Apart from the typo aspect, it's just unintuitive

How many people are using the ACCESS_2 hook? If you are, how are you using it? If it's behaviour

Reference: [1] and other places linked from there. My opinion: very low risk. My reason: exploiting

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think one clarification is needed: If you *are*