From: "Grant Likely" <glikely@gmail.com>
To: "David H. Lynch Jr" <dhlii@comcast.net>
Cc: Linux PPC <linuxppc-embedded@ozlabs.org>
Subject: Re: git tree
Date: Sat, 21 Apr 2007 23:43:40 -0600 [thread overview]
Message-ID: <528646bc0704212243x209ad132mb0a2338fa79783a4@mail.gmail.com> (raw)
In-Reply-To: <462AB3AF.2050509@comcast.net>
On 4/21/07, David H. Lynch Jr <dhlii@comcast.net> wrote:
> I am looking for something more like how to manage development with
> possibly multiple
> devices/projects.
> Not necescarily what is possible, but what Standard Operating
> Procedure for most developers.
The papers on http://www.jdl.com are very good at covering
collaboration with git. Take a look at them, and then feel free to
ask more questions.
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
prev parent reply other threads:[~2007-04-22 5:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070417022050.26A645C0062@mail41-blu.bigfish.com>
2007-04-17 7:48 ` git tree Grant Likely
2007-04-22 1:00 ` David H. Lynch Jr
2007-04-22 5:43 ` Grant Likely [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=528646bc0704212243x209ad132mb0a2338fa79783a4@mail.gmail.com \
--to=glikely@gmail.com \
--cc=dhlii@comcast.net \
--cc=linuxppc-embedded@ozlabs.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).