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

Status of git.git repository

From
Junio C Hamano <junkio@cox.net>
Date
Jul 30, 2005, 02:11 UTC
Message-ID
<7vhded6o0r.fsf@assigned-by-dhcp.cox.net>

I've been trying to streamline my workflow since I took it over from Linus, and I think I am getting used to it. So here is a short summary of what I am doing in the git.git repository.

Right now, there are two branches on kernel.org git.git repository. I would not rewind "master" so if I find out any screwups and need to do an emergency fix, that fix would go on top of the tip of "master" (I just did one today X-< due to lack of testing).

On the other hand, "pu" is rebased every time "master" advances. They are queued patches I receive in e-mails, and they hopefully will graduate to be part of "master" when I feel they look OK, and I feel that objections from the list were non-issues. Of course some may drop out without graduating. Please consider seeing your patch in "pu" branch an ACK from me, but seeing it sitting in "pu" for a long time is a sign of trouble.

By the way, do people mind my posting my own patches to the list? I keep the same in the "pu" (proposed updates) branch, so if the list readers think I am just adding noise to the list traffic, I would stop doing so, and instead just invite interested people to browse the "pu" branch.

Next: Petr Baudis
Message 1 of 2 in “Status of git.git repository”
  1. Junio C HamanoJul 30, 2005
  2. Petr BaudisAug 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.