git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tim Visher" <tim.visher@gmail.com>
To: git@vger.kernel.org
Subject: Hello All and Seeking Information
Date: Mon, 24 Nov 2008 11:28:22 -0500	[thread overview]
Message-ID: <c115fd3c0811240828y61e7bfecka1cacdd37865a4e8@mail.gmail.com> (raw)

Hello Everyone,

I'm new to the list so I figured I'd introduce myself instead of just
wall-flowering... "Hello"... :)

Anyway, I really like a lot of the concepts found in Git and the
reported power and flexibility of it are very intriguing.  However,
there are some issues that I can't wrap my head around, such as how
you can guarantee that all developers are working on the same
code-base without a central repo.  I would classify a lot of my issues
as paradigm rather than technically related. I understand a lot of
Git's underpinnings and the basic usage of it, I just can't wrap my
head around the higher-order parts of it.

I've done some Googling and I can't find a good 'Introduction to
Distributed SCM Concepts for Centralized SCM Developers' article yet.
Ideally, this would be an article all about the high-level thought
processes that go into utilizing Distributed SCM in a team environment
where having a single canonical representation of your project that
all developers are working off of is important.

Anyway, looking forward to participating.

P.S. Anyone want to tell me why the Git Mailing List was set-up
monolithically rather than the typical git-dev, git-user, git-admin,
git-x etc.?  I don't plan on hacking on Git so having the Dev mail in
the list is just noise for me.  I'm sure other people think that too.
Just wondering.

-- 

In Christ,

Timmy V.

http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail

             reply	other threads:[~2008-11-24 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 16:28 Tim Visher [this message]
2008-11-24 16:35 ` Hello All and Seeking Information Bruce Stephens
2008-11-24 16:39 ` Christian MICHON
2008-11-24 18:22 ` Jakub Narebski
2008-11-25  7:57 ` Pete Harlan

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=c115fd3c0811240828y61e7bfecka1cacdd37865a4e8@mail.gmail.com \
    --to=tim.visher@gmail.com \
    --cc=git@vger.kernel.org \
    /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).