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

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

From
Ping Yin <pkufranky@gmail.com>
Date
Nov 21, 2007, 13:17 UTC
Message-ID
<46dff0320711210517y282643a2q62819d3583ec9344@mail.gmail.com>
In-Reply-To
<46dff0320711210511g7d9febf5k47b082cc13bb905a@mail.gmail.com>
On Nov 21, 2007 9:11 PM, Ping Yin <pkufranky@gmail.com> wrote:
Show 13 quoted lines
> 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?
>

One more question: I see so many merges in pu branch, but where these merges go when a feature is moved to the master branch?

>
> --
> Ping Yin
>
-- 
Ping Yin
Previous: Ping YinNext: Theodore Tso
Message 2 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.