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

Re: rethinking patch management with GIT / topgit

From
Petr Baudis <pasky@suse.cz>
Date
Mar 22, 2010, 19:30 UTC
Message-ID
<20100322193035.GM3533@machine.or.cz>
In-Reply-To
<201003220859.41820.thomas@koch.ro>
On Mon, Mar 22, 2010 at 08:59:40AM +0100, Thomas Koch wrote:
> In all three cases you're free to either keep or throw away the old patchset.

Yes, but to the same degree e.g. with StGIT I'm free to keep the head of the old patch series. That does not mean the operation *preserves* the history, only that the history is still around somewhere in the repository, however it won't be around in other incarnations of the repository and it will not be connected in any way to the current version of the patchset.

Yes, if you are lucky you can figure out the name of the previous version, but it's like starting development of each new kernel version by a clean import of the sources.

-- 
				Petr "Pasky" Baudis
http://pasky.or.cz/ | "Ars longa, vita brevis." -- Hippocrates
Previous: Thomas KochNext: Thomas Koch
Message 6 of 7 in “rethinking patch management with GIT / topgit”
  1. Thomas KochMar 20, 2010
  2. Petr BaudisMar 20, 2010
  3. Thomas KochMar 20, 2010
  4. Petr BaudisMar 21, 2010
  5. Thomas KochMar 22, 2010
  6. Petr BaudisMar 22, 2010
  7. Thomas KochMar 23, 2010

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.