git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [doc]playing with git, and netdev/libata-dev trees

From
Dave Airlie <airlied@gmail.com>
Date
Jun 4, 2005, 08:40 UTC
Message-ID
<21d7e99705060401405cfd5a11@mail.gmail.com>
In-Reply-To
<42955DF7.4000805@pobox.com>
Show 11 quoted lines
> 
> 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.
Previous: James PurserNext: Jeff Garzik
Message 4 of 7 in “[doc][git] playing with git, and netdev/libata-dev trees”
  1. Jeff GarzikMay 26, 2005
  2. Frank SorensonMay 26, 2005
  3. James PurserMay 26, 2005
  4. Dave AirlieJun 4, 2005
  5. Jeff GarzikJun 4, 2005
  6. Dave AirlieJun 4, 2005
  7. Jeff GarzikJun 4, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.