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

Merging five months of Linux kernel history

From
JGJan-Benedict Glaw <jbglaw@lug-owl.de>
Date
Oct 29, 2006, 19:32 UTC
Message-ID
<20061029193228.GR26271@lug-owl.de>
Hi!

Due to a move to a new flat and other reasons, I wasn't able to do daily merges from Linus's tree into our vax-linux tree. My time situation has improved and I want to merge all the new and shiny stuff, but it seems a straight "git pull" isn't the best way to do that.

What I'd actually love to do is to go through all commits since the last merge and pull/accept/cherry-pick then one by one. That way I'll learn about new stuff. I'll specifically see generic changes that imply arch-specific stuff, things I'll need to implement later on.

Is there any sane way to cluse such a large gap? I don't mind looking through tenthousands of commits, as long as I get a chance to spot "important" ones.

Thanks, JBG
-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:            http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
the second  :
Next: Junio C Hamano
Message 1 of 4 in “Merging five months of Linux kernel history”
  1. Jan-Benedict GlawOct 29, 2006
  2. Junio C HamanoOct 29, 2006
  3. Jan-Benedict GlawOct 30, 2006
  4. Junio C HamanoOct 30, 2006

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.