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

Re: [PATCH (topgit)] tg-patch: add support for generating patches against worktree and index

From
MKmartin f krafft <madduck@madduck.net>
Date
Jan 21, 2009, 03:20 UTC
Message-ID
<20090121032052.GB7422@lapse.rw.madduck.net>
In-Reply-To
<20090120175635.GA5721@roro3.zxlink>
also sprach Kirill Smelkov <kirr@landau.phys.spbu.ru> [2009.01.21.0456 +1100]:
> No problem and take your time.
> 
> It was just me having no idea about what's going on.

I am a little confused about the patches, and git-am does not seem to be able to apply two patches from the same email. I use Maildir, so I am passing the single message with multiple patches to git-am, and it applies all changes into one single commit.

Anyway, do you have a repo which I can cherry-pick from?
-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"out of the crooked timber of humanity,
 no straight thing was ever made."
                                                       -- imanuel kant
 
spamtraps: madduck.bogus@madduck.net
Previous: Kirill SmelkovNext: Kirill Smelkov
Message 8 of 10 in “tg-patch: add support for generating patches against worktree and index”
  1. tg-patch: add support for generating patches against worktree and indexKirill Smelkov, Jan 8, 2009
  2. martin f krafftJan 8, 2009
  3. Kirill SmelkovJan 8, 2009
  4. Kirill SmelkovJan 8, 2009
  5. Kirill SmelkovJan 18, 2009
  6. martin f krafftJan 20, 2009
  7. Kirill SmelkovJan 20, 2009
  8. martin f krafftJan 21, 2009
  9. Kirill SmelkovJan 21, 2009
  10. martin f krafftJan 22, 2009

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.