From: Sitaram Chamarty <sitaramc@gmail.com>
To: Jon Forrest <nobozo@gmail.com>, git@vger.kernel.org
Subject: Re: [ANN] Pro Git Reedited 2nd Edition
Date: Sat, 13 Aug 2016 06:00:21 +0530 [thread overview]
Message-ID: <0e542a52-16ed-8967-fe1d-bfb5a728518c@gmail.com> (raw)
In-Reply-To: <be1b1fcd-48d7-facd-f45c-0c52e6c12e88@gmail.com>
On 08/12/2016 08:07 PM, Jon Forrest wrote:
>
>
> 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.
Oh ok; I must have misunderstood what "2nd edition" means, or did not read your
original email carefully enough.
prev parent reply other threads:[~2016-08-13 0:30 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
2016-08-13 0:30 ` Sitaram Chamarty [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=0e542a52-16ed-8967-fe1d-bfb5a728518c@gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=nobozo@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.
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 NNTP newsgroup(s).