From: "Carlos Martín Nieto" <carlos@cmartin.tk>
To: Joshua Stoutenburg <jehoshua02@gmail.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>, Git List <git@vger.kernel.org>
Subject: Re: Anybody home?
Date: Thu, 15 Sep 2011 11:43:56 +0200 [thread overview]
Message-ID: <1316079837.2019.18.camel@bee.lab.cmartin.tk> (raw)
In-Reply-To: <CAOZxsTqGt=gYr3t7e5Ma4z6W9wt_JxrgsNSGFGVbtk2rc3LZ9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
On Thu, 2011-09-15 at 02:01 -0700, Joshua Stoutenburg wrote:
> > Reading your exchanges elsewhere in this thread, I think you missed that
> > you don't need a git server at all just to *use* git.
> >
> > Even when you want to exchange your commits between two or three machines,
> > all you need is ssh access. There is no *git server* necessary. git is not
> > svn. ;-)
> >
> > I thought I'd just mention this to help you streamline your search.
> >
> > -- Hannes
> >
>
> I read the first four and a half chapters from the Pro Git book pdf.
> So I think I understood that much.
>
> But in my situation, I do need a server so that other developers can
> access anytime over the internet.
If the code shouldn't be made public, then you should take a look at
gitolite[0]. Otherwise, you can just host it on gitorious.org or
github.com
[0] https://github.com/sitaramc/gitolite
cmn
>
> I should have mentioned that.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-09-15 9:44 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
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 [this message]
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=1316079837.2019.18.camel@bee.lab.cmartin.tk \
--to=carlos@cmartin.tk \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=jehoshua02@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).