From: "Christian MICHON" <christian.michon@gmail.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Query: GIT bare repro
Date: Wed, 6 Aug 2008 10:29:09 +0200 [thread overview]
Message-ID: <46d6db660808060129u754488d3jda27e3873154c533@mail.gmail.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608701C2C85A14@dbde02.ent.ti.com>
On Wed, Aug 6, 2008 at 9:46 AM, Pandita, Vikram <vikram.pandita@ti.com> wrote:
> Hi GIT users
>
> I want to use GIT for my team for distributed development.
> The team members are working at different sites.
>
> Would appreciate help on following:
>
> 1) Could you point me to some document/example for doing so? This should be very common scenario I assume.
Please read http://book.git-scm.com/3_distributed_workflows.html
--
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
next prev parent reply other threads:[~2008-08-06 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 6:26 What's in git.git (Aug 2008, #01; Tue, 05) Junio C Hamano
2008-08-06 7:46 ` Query: GIT bare repro Pandita, Vikram
2008-08-06 8:29 ` Christian MICHON [this message]
2008-08-06 9:15 ` Pandita, Vikram
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=46d6db660808060129u754488d3jda27e3873154c533@mail.gmail.com \
--to=christian.michon@gmail.com \
--cc=git@vger.kernel.org \
--cc=vikram.pandita@ti.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).