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

Re: Stacked GIT 0.1 (a.k.a. quilt for git)

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Jun 17, 2005, 22:10 UTC
Message-ID
<Pine.LNX.4.21.0506171750180.30848-100000@iabervon.org>
In-Reply-To
<tnxy899zzu7.fsf@arm.com>
On Thu, 16 Jun 2005, Catalin Marinas wrote:
> StGIT is a Python application providing similar functionality to quilt
> (i.e. pushing/poping patches to a stack) on top of git.

It might be worth making the system work for having multiple series in the same tree. You could do this by saving the base commit for .git/refs/heads/<name> as .git/refs/bases/<name>, and putting patches in .git/patches/<name>/. Some people do a lot with .git/refs/heads/something; I, at least, symlink .git/HEAD to whichever one I'm using, so that might be the right way to tell what the user is doing.

I think it would worth exploring defining a git type for patches and storing the patches inside git as well. Then a commit could identify the patch it applies (when it is from applying a patch), and a rebased patch could reference the patch it replaces, and then (with a certain amount of handwaving of implementation) the system could notice when the patch you're pushing got applied upstream. Or, at least, git could avoid throwing away the history information when it goes through patches. I keep thinking that this would be an important feature, but I haven't got the familiarity with quilt to know how it should work.

	-Daniel
*This .sig left intentionally blank*
Previous: Catalin MarinasNext: Jon Seymour
Message 2 of 15 in “Stacked GIT 0.1 (a.k.a. quilt for git)”
  1. Catalin MarinasJun 16, 2005
  2. Daniel BarkalowJun 17, 2005
  3. Jon SeymourJun 17, 2005
  4. Catalin MarinasJun 18, 2005
  5. Catalin MarinasJun 18, 2005
  6. Daniel BarkalowJun 19, 2005
  7. Catalin MarinasJun 19, 2005
  8. Paul JacksonJun 24, 2005
  9. Catalin MarinasJun 24, 2005
  10. Paul JacksonJun 24, 2005
  11. Catalin MarinasJun 24, 2005
  12. Paul JacksonJun 24, 2005
  13. Catalin MarinasJun 24, 2005
  14. Catalin MarinasJun 28, 2005
  15. Paul JacksonJun 29, 2005

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.