From: Jakub Narebski <jnareb@gmail.com>
To: Joshua Stoutenburg <jehoshua02@gmail.com>
Cc: Michael Witten <mfwitten@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: Anybody home?
Date: Thu, 15 Sep 2011 04:04:49 -0700 (PDT) [thread overview]
Message-ID: <m3y5xqrro0.fsf@localhost.localdomain> (raw)
In-Reply-To: <CAOZxsTrsi5mNdm8OgvfXyYwj1T4Vw3HfQGN-5Dsb+QnX0nz4ag@mail.gmail.com>
Couldn't you pick up less descriptive subject ;-) ?
Joshua Stoutenburg <jehoshua02@gmail.com> writes:
> On Wed, Sep 14, 2011 at 9:48 PM, Michael Witten <mfwitten@gmail.com> wrote:
>> On Thu, Sep 15, 2011 at 04:24, Joshua Stoutenburg <jehoshua02@gmail.com> wrote:
>>> I'm having a hard time understanding clearly how to set up a git
>>> server and configure my local machine to pull and push to it.
> There seems to be a plethora of documentation on git from various sources.
>
> See what I mean:
> http://git-scm.com/documentation
> http://progit.org/book/
> http://gitref.org/
> http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html
> http://www.kernel.org/pub/software/scm/git/docs/everyday.html
> http://git-scm.com/course/svn.html
> http://hoth.entp.com/output/git_for_designers.html
> http://eagain.net/articles/git-for-computer-scientists/
> http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
> http://www-cs-students.stanford.edu/~blynn/gitmagic/
> http://help.github.com/
> http://www.kernel.org/pub/software/scm/git/docs/
> http://refcardz.dzone.com/refcardz/getting-started-git
>
> Which source makes the least amount of assumptions and offers all the
> juicy details for configuring git on the server, and git on the local
> machine, without any fluff?
>
> I'm looking for a solid guide. Not a novel. Not a pamphlet.
I think that either "Pro Git" book, or "The Git Community Book"
would be a best source to learn about setting-up git server.
I think the simplest solution for git hosting management would be to
use gitolite (there are other git repository management software:
Gitosis, SCM Manager, Gitblit).
If you want to host something like GitHub, there are open source
solutions too: Gitorious, InDefero, Girocco + gitweb,...
HTH
--
Jakub Narębski
next prev parent reply other threads:[~2011-09-15 11:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 4:24 Anybody home? Joshua Stoutenburg
2011-09-15 4:48 ` Michael Witten
2011-09-15 5:04 ` Joshua Stoutenburg
2011-09-15 5:06 ` Joshua Stoutenburg
2011-09-15 5:21 ` Alexander Kostikov
[not found] ` <CAGAhT3mo0qqU9WMgfM1vKjwMtjeb55LRG1QfEYhq7JwsBSGSEw@mail.gmail.com>
2011-09-15 5:37 ` Joshua Stoutenburg
2011-09-15 12:55 ` Ted Ts'o
2011-09-15 11:04 ` Jakub Narebski [this message]
2011-09-15 7:15 ` Johannes Sixt
2011-09-15 7:48 ` Thomas Rast
2011-09-15 9:42 ` Joshua Stoutenburg
2011-09-15 13:17 ` Martin Langhoff
2011-09-15 9:01 ` Joshua Stoutenburg
2011-09-15 9:43 ` Carlos Martín Nieto
2011-09-15 9:51 ` Joshua Stoutenburg
2011-09-15 10:54 ` Miles Bader
2011-09-15 11:34 ` Carlos Martín Nieto
2011-09-15 12:01 ` Joshua Stoutenburg
2011-09-15 15:04 ` Scott Chacon
2011-09-15 21:00 ` Joshua Stoutenburg
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=m3y5xqrro0.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jehoshua02@gmail.com \
--cc=mfwitten@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).