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

Re: [Core GIT] Long-term cherrypicking

From
Petr Baudis <pasky@suse.cz>
Date
Sep 22, 2005, 09:58 UTC
Message-ID
<20050922095845.GE21019@pasky.or.cz>
In-Reply-To
<tnxpsr12zu0.fsf@arm.com>

Dear diary, on Thu, Sep 22, 2005 at 11:53:27AM CEST, I got a letter where Catalin Marinas <catalin.marinas@gmail.com> told me that...

Show 5 quoted lines
> But what I understand from Petr's e-mail is that re-basing the patches
> is not acceptable for a repository which is public. One option would
> be to keep a private tree where the patches are re-based and a public
> one which periodically pulls from Linus' tree and your private
> one. Not sure how complicated the commit graph would look.

It would be pretty ugly since the same patches would re-appear in the commit graph in another incarnations many times.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
Previous: Catalin MarinasNext: Catalin Marinas
Message 7 of 8 in “[Core GIT] Long-term cherrypicking”
  1. Petr BaudisSep 21, 2005
  2. Junio C HamanoSep 21, 2005
  3. Petr BaudisSep 21, 2005
  4. Junio C HamanoSep 21, 2005
  5. Greg KHSep 22, 2005
  6. Catalin MarinasSep 22, 2005
  7. Petr BaudisSep 22, 2005
  8. Catalin MarinasSep 22, 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.