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

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

From
Yann Dirson <ydirson@altern.org>
Date
Nov 3, 2007, 14:28 UTC
Message-ID
<20071103142851.GG26436@nan92-1-81-57-214-146.fbx.proxad.net>
In-Reply-To
<b0943d9e0711030356j4dcd31cbl54d838107240b3d0@mail.gmail.com>
On Sat, Nov 03, 2007 at 10:56:36AM +0000, Catalin Marinas wrote:
Show 9 quoted lines
> On 26/10/2007, Karl Hasselström <kha@treskal.com> wrote:
> > I wanted to build an StGit command that coalesced adjacent patches to
> > a single patch. Because the end result tree would still be the same,
> > this should be doable without ever involving HEAD, the index, or the
> > worktree.
> 
> Wouldn't HEAD need to be modified since the commit log changes
> slightly, even though the tree is the same. Or am I misunderstanding
> this?

This reminds me of someone suggesting that some patches could be represented by more than one commit. 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 ?

Best regards,
-- 
Yann
Previous: Catalin MarinasNext: Karl Hasselström
Message 3 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.