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

What is the whole process of cooking git as a maintainer?

From
Ping Yin <pkufranky@gmail.com>
Date
Nov 21, 2007, 13:11 UTC
Message-ID
<46dff0320711210511g7d9febf5k47b082cc13bb905a@mail.gmail.com>

I have scanned the manual and found a 'Linux subsystem maintainer' example. However, that's a little brief and i wonder a more real example. I think an example of how to cook git as a maintainer is better.

Junio , could you please share the whole process of cooking among pu, next and master? Or, can i find this in the mail list archive?

For example: In which branch the test is performed? How to rewind pu? How to merge a subset of changes from pu to next, and from next to master?

-- 
Ping Yin
Next: Ping Yin
Message 1 of 10 in “What is the whole process of cooking git as a maintainer?”
  1. Ping YinNov 21, 2007
  2. Ping YinNov 21, 2007
  3. Theodore TsoNov 21, 2007
  4. Johannes SchindelinNov 21, 2007
  5. Addendum to "MaintNotes"Junio C Hamano, Nov 22, 2007
  6. Jeff KingNov 22, 2007
  7. Junio C HamanoNov 22, 2007
  8. David KastrupNov 22, 2007
  9. Jeff KingNov 22, 2007
  10. Jeff KingNov 22, 2007

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.