git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jon Forrest <nobozo@gmail.com>
To: Sitaram Chamarty <sitaramc@gmail.com>, git@vger.kernel.org
Subject: Re: [ANN] Pro Git Reedited 2nd Edition
Date: Fri, 12 Aug 2016 07:37:15 -0700	[thread overview]
Message-ID: <be1b1fcd-48d7-facd-f45c-0c52e6c12e88@gmail.com> (raw)
In-Reply-To: <d2ef9717-beb2-2661-d0b0-4e33f82511ae@gmail.com>



On 8/12/16 6:11 AM, Sitaram Chamarty wrote:

> At present gitolite is -- AFAIK -- the only "pure server side", "no GUI"
> solution for access control, and has some interesting features that more
> "GUI" solutions may not.  It is also (again, AFAIK) used by kernel.org,
> Fedora, Gentoo, and several other open source projects as well as many
> enterprises.
>
> If you're ok with adding that, I'd be happy to supply some text for your
> consideration.

I appreciate your offer and I don't disagree with what you're
suggesting, but my goal, for now at least, is to keep the same coverage 
as upstream.

If they add something about Gitolite to their next edition, then
I will also.

Cordially,
Jon Forrest


  reply	other threads:[~2016-08-12 14:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24  4:07 [ANN] Pro Git Reedited 2nd Edition Jon Forrest
2016-07-24  9:00 ` Jakub Narębski
     [not found]   ` <6f7eea6b-2446-5740-cbec-141d71a33ea1@gmail.com>
2016-07-24 17:19     ` Jakub Narębski
2016-07-24 17:34       ` Jon Forrest
2016-07-24 18:27         ` Jakub Narębski
2016-07-24 18:41           ` Jon Forrest
2016-07-25  7:04             ` Johannes Schindelin
2016-07-24 20:03           ` Jon Forrest
2016-07-26  9:15 ` Manlio Perillo
2016-07-26 14:22   ` Jon Forrest
2016-08-12 13:11 ` Sitaram Chamarty
2016-08-12 14:37   ` Jon Forrest [this message]
2016-08-13  0:30     ` Sitaram Chamarty

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: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=be1b1fcd-48d7-facd-f45c-0c52e6c12e88@gmail.com \
    --to=nobozo@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sitaramc@gmail.com \
    /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://80x24.org/mirrors/git.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).