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

Re: STG, problem with pop/push of alternative versions of a patch

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
Sep 15, 2007, 22:44 UTC
Message-ID
<b0943d9e0709151544p1f40508cqad2663416187e15@mail.gmail.com>
In-Reply-To
<9e4733910709151042p7c681e25o386be2ca2719daa9@mail.gmail.com>
On 15/09/2007, Jon Smirl <jonsmirl@gmail.com> wrote:
> I was not happy when my patch disappeared. Luckily I had exported it a
> little while earlier.

Otherwise, the patch log should be present and it shows each commit id of the patch.

Since we are at this, I think we need a config option to automatically back up (export) the patches. Since StGIT detects whether the patch applied cleanly or it was modified (with a diff3 merge), it only needs to export in a few cases and not affect the performance (diff3 takes significantly longer anyway).

Thanks for reporting this issue.
-- 
Catalin
Previous: Jon Smirl
Message 6 of 6 in “STG, problem with pop/push of alternative versions of a patch”
  1. Jon SmirlSep 15, 2007
  2. Catalin MarinasSep 15, 2007
  3. Jon SmirlSep 15, 2007
  4. Catalin MarinasSep 15, 2007
  5. Jon SmirlSep 15, 2007
  6. Catalin MarinasSep 15, 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.