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

Re: [StGit RFC] A more structured way of calling git

From
Karl Hasselström <kha@treskal.com>
Date
Nov 16, 2007, 08:36 UTC
Message-ID
<20071116083621.GA18039@diana.vm.bytemark.co.uk>
In-Reply-To
<20071116074255.GA16975@diana.vm.bytemark.co.uk>
On 2007-11-16 08:42:55 +0100, Karl Hasselström wrote:
Show 8 quoted lines
> The complete state that would have to be saved would be
>
>   * (patchname, commit sha1) pairs for all patches
>
>   * (branchname, branch head sha1) pair
>
>   * the ordered lists of applied, unapplied, and eventually also
>     hidden patches
Oh, and
  * .git/config (one blob)
  * the worktree (one tree object?)
  * the index (one tree object per stage?)

Otherwise, we won't be able to un-clobber them. But a first implementation could certainly skip this part.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Karl Hasselström
Message 8 of 8 in “[StGit RFC] A more structured way of calling git”
  1. Karl HasselströmOct 26, 2007
  2. Catalin MarinasNov 3, 2007
  3. Yann DirsonNov 3, 2007
  4. Karl HasselströmNov 4, 2007
  5. Karl HasselströmNov 4, 2007
  6. Catalin MarinasNov 15, 2007
  7. Karl HasselströmNov 16, 2007
  8. Karl HasselströmNov 16, 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.