emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien Guerry <bzg@gnu.org>
To: Ian Barton <lists@wilkesley.net>
Cc: Arun Isaac <arunisaac@systemreboot.net>,
	emacs-orgmode@gnu.org, Konstantin Kliakhandler <kosta@slumpy.org>,
	Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Why no secure code retrieval
Date: Sun, 03 Jul 2016 09:09:40 +0200	[thread overview]
Message-ID: <87eg7bnqob.fsf@free.fr> (raw)
In-Reply-To: <20160702165130.GA1401@scamper2.bantercat.co.uk> (Ian Barton's message of "Sat, 2 Jul 2016 17:51:30 +0100")

Hi Ian,

Ian Barton <lists@wilkesley.net> writes:

> Not heard of Gogs before, although it looks nice. Another possiblity
> would be gitolite with cgit. Gitolite is very flexible and as a
> consequence can be hard to set up initially. The documentation is very
> comprehensive. It supports mirroring of repos.

I have no experience with gitolite.

I encourage you to try gogs, it is very easy to install and maintain,
and its interface is very engaging.  The more gogs users and potential
admins out there, the more comfortable I'll feel making the switch.

-- 
 Bastien

  reply	other threads:[~2016-07-03  7:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 12:10 Why no secure code retrieval Konstantin Kliakhandler
2016-06-29  6:11 ` Arun Isaac
2016-06-30 11:50   ` Nicolas Goaziou
2016-07-02 14:18     ` Bastien Guerry
2016-07-02 16:51       ` Ian Barton
2016-07-03  7:09         ` Bastien Guerry [this message]
2016-07-03 15:11           ` Robert Klein
2016-07-03 15:20           ` Achim Gratz
2016-07-03 16:57           ` Robert Horn
2016-07-03 18:18             ` Konstantin Kliakhandler
2016-07-03 18:25               ` Achim Gratz
2016-07-03 20:12               ` Robert Horn
2016-07-03 22:36                 ` Konstantin Kliakhandler
2016-07-04  0:17                   ` Robert Horn
2016-07-04  6:15                     ` Konstantin Kliakhandler

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://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eg7bnqob.fsf@free.fr \
    --to=bzg@gnu.org \
    --cc=arunisaac@systemreboot.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=kosta@slumpy.org \
    --cc=lists@wilkesley.net \
    --cc=mail@nicolasgoaziou.fr \
    /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/emacs/org-mode.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).