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

Re: stgit: lost all my patches again

From
Jon Smirl <jonsmirl@gmail.com>
Date
Oct 4, 2007, 12:10 UTC
Message-ID
<9e4733910710040510v53cd390el35cf5b4251e6d@mail.gmail.com>
In-Reply-To
<20071004083304.GB17778@diana.vm.bytemark.co.uk>
On 10/4/07, Karl Hasselström <kha@treskal.com> wrote:
Show 9 quoted lines
> On 2007-10-04 01:29:17 -0400, Jon Smirl wrote:
>
> > for some reason the refresh from that command didn't close. Then stg
> > pushed all the patches back after the edit and they got included
> > into that patch.
>
> That's really weird. As far as I know there isn't a concept of
> "closed" patches in StGit -- there's no need, because they're always
> closed!

Must be the other way around then, the next nine patches didn't get opened right. Their descriptions ended up in the right place but the deltas all ended up in the first patch.

Show 14 quoted lines
> > I did the 'stg refresh' from a directory that was not being tracked
> > by git. It is in the .gitignore list. This appears to be the root of
> > the problem.
>
> Mmmph. This is not the only StGit command that's apparently not safe
> to run from a subdirectory. See e.g. https://gna.org/bugs/?9986.
>
> I plan to do some StGit hacking this weekend. I guess subdirectory
> safeness ought to be at the top of my list ...
>
> --
> Karl Hasselström, kha@treskal.com
>       www.treskal.com/kalle
>
-- 
Jon Smirl
jonsmirl@gmail.com
Previous: Karl HasselströmNext: Jon Smirl
Message 3 of 7 in “stgit: lost all my patches again”
  1. Jon SmirlOct 4, 2007
  2. Karl HasselströmOct 4, 2007
  3. Jon SmirlOct 4, 2007
  4. Jon SmirlOct 4, 2007
  5. Karl HasselströmOct 4, 2007
  6. David BrownOct 4, 2007
  7. Karl HasselströmOct 4, 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.