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

Re: Re-done kernel archive - real one?

From
Greg KH <greg@kroah.com>
Date
Apr 18, 2005, 22:14 UTC
Message-ID
<20050418221407.GA20290@kroah.com>
In-Reply-To
<20050418220541.GB19744@kroah.com>
On Mon, Apr 18, 2005 at 03:05:41PM -0700, Greg KH wrote:
Show 29 quoted lines
> On Mon, Apr 18, 2005 at 08:42:14AM -0700, Linus Torvalds wrote:
> > 
> > 
> > On Mon, 18 Apr 2005, Greg KH wrote:
> > >
> > > On Sun, Apr 17, 2005 at 04:24:24PM -0700, Linus Torvalds wrote:
> > > > 
> > > > Tools absolutely matter. And it will take time for us to build up that 
> > > > kind of helper infrastructure. So being newbie might be part of it, but 
> > > > it's the smaller part, I say. Rough interfaces is a big issue.
> > > 
> > > Speaking of tools, you had a "dotest" program to apply patches in email
> > > form to a bk tree.  And from what I can gather, you've changed that to
> > > handle git archives, right?
> > 
> > Yup.
> > 
> > It's a git archive at 
> > 
> > 	kernel.org:/pub/linux/kernel/people/torvalds/git-tools.git
> > 
> > and it seems to work. It's what I've used for all the kernel patches 
> > (except for the merge), and it's what I use for the git stuff that shows 
> > up as authored by others.
> 
> Hm, have you pushed all of the recent changes public?  I get the
> following when trying to apply a patch:
> $ ../git-tools/dotest < ~/linux/patches/usb/usb-visor-tapwave_zodiac.patch 
>  mailsplit <mbox> <directory>
Doh, you want it as a command line argument now.  Stupid me...
Anyway, I try it this way and get:
$ dotest ~/linux/patches/usb/usb-visor-tapwave_zodiac.patch             
Applying USB: visor Tapwave Zodiac support patch
fatal: preparing to update file 'drivers/usb/serial/visor.c' not uptodate in cache
What did I forget to do?
thanks,
greg k-h
Previous: Greg KHNext: Linus Torvalds
Message 53 of 60 in “Re-done kernel archive - real one?”
  1. Linus TorvaldsApr 16, 2005
  2. Russell KingApr 17, 2005
  3. Petr BaudisApr 17, 2005
  4. Linus TorvaldsApr 17, 2005
  5. Russell KingApr 17, 2005
  6. Linus TorvaldsApr 17, 2005
  7. Linus TorvaldsApr 17, 2005
  8. Russell KingApr 17, 2005
  9. Linus TorvaldsApr 17, 2005
  10. Russell KingApr 17, 2005
  11. Linus TorvaldsApr 17, 2005
  12. Russell KingApr 17, 2005
  13. Russell KingApr 18, 2005
  14. Petr BaudisApr 18, 2005
  15. Linus TorvaldsApr 18, 2005
  16. Petr BaudisApr 18, 2005
  17. Russell KingApr 17, 2005
  18. Linus TorvaldsApr 17, 2005
  19. David A. WheelerApr 17, 2005
  20. Petr BaudisApr 17, 2005
  21. Russell KingApr 17, 2005
  22. David A. WheelerApr 17, 2005
  23. Martin SchlemmerApr 18, 2005
  24. H. Peter AnvinApr 17, 2005
  25. Jochen RoemlingApr 17, 2005
  26. Randy.DunlapApr 17, 2005
  27. Petr BaudisApr 17, 2005
  28. David WoodhouseApr 17, 2005
  29. Linus TorvaldsApr 17, 2005
  30. Russell KingApr 17, 2005
  31. Russell KingApr 17, 2005
  32. Linus TorvaldsApr 17, 2005
  33. Russell KingApr 18, 2005
  34. Martin SchlemmerApr 18, 2005
  35. Petr BaudisApr 18, 2005
  36. Linus TorvaldsApr 18, 2005
  37. Linus TorvaldsApr 18, 2005
  38. Petr BaudisApr 18, 2005
  39. Russell KingApr 18, 2005
  40. Linus TorvaldsApr 18, 2005
  41. Petr BaudisApr 18, 2005
  42. Russell KingApr 18, 2005
  43. Petr BaudisApr 18, 2005
  44. Russell KingApr 19, 2005
  45. Linus TorvaldsApr 18, 2005
  46. Russell KingApr 18, 2005
  47. Linus TorvaldsApr 18, 2005
  48. Petr BaudisApr 18, 2005
  49. Greg KHApr 18, 2005
  50. Randy.DunlapApr 18, 2005
  51. Linus TorvaldsApr 18, 2005
  52. Greg KHApr 18, 2005
  53. Greg KHApr 18, 2005
  54. Linus TorvaldsApr 18, 2005
  55. Greg KHApr 18, 2005
  56. Linus TorvaldsApr 18, 2005
  57. H. Peter AnvinApr 17, 2005
  58. randy_dunlapApr 17, 2005
  59. David WoodhouseApr 17, 2005
  60. randy_dunlapApr 18, 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.