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 4, 2007, 18:40 UTC
Message-ID
<20071104184003.GB6032@diana.vm.bytemark.co.uk>
In-Reply-To
<20071103142851.GG26436@nan92-1-81-57-214-146.fbx.proxad.net>
On 2007-11-03 15:28:51 +0100, Yann Dirson wrote:
> This reminds me of someone suggesting that some patches could be
> represented by more than one commit.

You might be remebering me pointing out that the old infrastructure supported (or at least not directly disallowed) this.

> But I'm not sure such a beast would be useful - I fear that would
> make StGIT much more complicated, but would it really make things
> better?

Yes, it makes everything much more complicated, and no, it doesn't buy us anything new. After all, once we know the parent and the tree we want a patch to have, we can just manufacture a commit that has that tree and that parent.

My proposed new infrastructure cannot represent such patches, very much by design.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Yann DirsonNext: Karl Hasselström
Message 4 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.