From: "David H. Lynch Jr" <dhlii@comcast.net>
To: Grant Likely <glikely@gmail.com>
Cc: Linux PPC <linuxppc-embedded@ozlabs.org>
Subject: Re: git tree
Date: Sat, 21 Apr 2007 21:00:31 -0400 [thread overview]
Message-ID: <462AB3AF.2050509@comcast.net> (raw)
In-Reply-To: <528646bc0704170048u25cd535ar783c737bb47d9fdf@mail.gmail.com>
Grant Likely wrote:
> I haven't quite decided yet. The -temac and -sysace branches are a
> bit of an experiment. I thought it might be a good idea to maintain
> the drivers in seperate branches so it is easy to get a diff on just
> that driver; but the individual drivers are pretty seperate anyway (in
> different directories). I think I'll probably drop the -temac and
> -sysace branches, and just maintain all my changes in the -dev branch.
> The -forupstream branch is specifically for patches that are due to
> go upstream. I'll add patches there when I think they are suitable
> for mainline, and post them to the list.
I would greatly appreciate pointers to so reference for using git
for kernel development.
I have looked through most of the howto's and have a basic
competence with git.
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.
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next prev parent reply other threads:[~2007-04-22 1:10 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 [this message]
2007-04-22 5:43 ` Grant Likely
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=462AB3AF.2050509@comcast.net \
--to=dhlii@comcast.net \
--cc=glikely@gmail.com \
--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).