From: Dave Airlie <airlied@gmail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [doc]playing with git, and netdev/libata-dev trees
Date: Sat, 4 Jun 2005 18:40:40 +1000 [thread overview]
Message-ID: <21d7e99705060401405cfd5a11@mail.gmail.com> (raw)
In-Reply-To: <42955DF7.4000805@pobox.com>
>
> When I merge a patch for drivers/net/forcedeth.c, I merge it into a
> brand new 'forcedeth' repository, a peer to the 40+ other such
> repository. Under BitKeeper, I made these repositories available merged
> together into one big "netdev-2.6" repository because it was too time
> consuming to make the individual 50+ trees publicly available. With
> git, developers have direct access to the individual trees.
>
> I thought I would write up a quick guide describing how to mess around
> with the netdev and libata-dev trees, and with git in general.
>
Thanks for this, I'm starting to get up to speed on git now...
Two questions,
1. when you want to publish your tree what do you do? just rsync it
onto kernel.org?
2. When you are taking things from your queue for Linus do you create
another tree and merge your branches into it or what?
Dave.
next prev parent reply other threads:[~2005-06-04 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 5:26 [doc][git] playing with git, and netdev/libata-dev trees Jeff Garzik
2005-05-26 8:19 ` [doc]playing " Frank Sorenson
2005-05-26 11:54 ` James Purser
2005-06-04 8:40 ` Dave Airlie [this message]
2005-06-04 10:26 ` Jeff Garzik
2005-06-04 10:31 ` Dave Airlie
2005-06-04 18:16 ` Jeff Garzik
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=21d7e99705060401405cfd5a11@mail.gmail.com \
--to=airlied@gmail.com \
--cc=akpm@osdl.org \
--cc=git@vger.kernel.org \
--cc=linux-kernel@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).