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

Re: [StGit PATCH 1/2] Convert "stg refresh" to the new infrastructure

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
Jun 29, 2008, 09:42 UTC
Message-ID
<b0943d9e0806290242q1bc8aa67qb3523221b3db70e2@mail.gmail.com>
In-Reply-To
<20080625042337.6044.53357.stgit@yoghurt>
2008/6/25 Karl Hasselström <kha@treskal.com>:
Show 5 quoted lines
> And in the process, make it more powerful: it will now first create a
> temp patch containing the updates, and then try to merge it into the
> patch to be updated. If that patch is applied, this is done by
> popping, pushing, and coalescing; if it is unapplied, it is done with
> an in-index merge.

Does it make sense to refresh an unapplied patch? Maybe adding a new file to the patch but I don't really see a need for this.

> Also, whenever path limiting is used, we will now use a temporary
> index in order to avoid including all staged updates (since they may
> touch stuff outside the path limiters).

I haven't checked but what is the behaviour in subdirectors? It currently refreshes everythink unless "." is specified so that it will only refresh the current subdirectory.

The patch looks fine otherwise.
-- 
Catalin
Previous: Karl HasselströmNext: Karl Hasselström
Message 3 of 6 in “Convert "stg refresh" to the new infrastructure”
  1. 1/2 Convert "stg refresh" to the new infrastructureKarl Hasselström, Jun 25, 2008
  2. 2/2 New refresh testsKarl Hasselström, Jun 25, 2008
  3. Catalin MarinasJun 29, 2008
  4. Karl HasselströmJun 29, 2008
  5. Catalin MarinasJun 29, 2008
  6. Karl HasselströmJun 29, 2008

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.