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

[PATCH 0/2] allow patches called "applied", "current", and so on

From
CLChuck Lever <cel@citi.umich.edu>
Date
Jan 29, 2006, 18:10 UTC
Message-ID
<20060129181004.1919.92166.stgit@dexter.citi.umich.edu>

The following patches create a separate directory for patches so that patch names like "applied" don't collide with the patch series control files.

A new option on the "stg branch" command allows users to convert between the old-style (all in the same series directory) and the new-style (patches in a separate directory). "stg" should be good at detecting which type of repository is in use and adapting to it, so this change should be entirely invisible on legacy repositories.

        -- Chuck Lever
--
corporate:    <cel at netapp dot com>
personal:     <chucklever at bigfoot dot com>
Next: Chuck Lever
Message 1 of 3 in “allow patches called "applied", "current", and so on”
  1. 0/2 allow patches called "applied", "current", and so onChuck Lever, Jan 29, 2006
  2. 1/2 Use a separate directory for patches under each branch subdirChuck Lever, Jan 29, 2006
  3. 2/2 Add an option to "stg branch" to convert the internal formatChuck Lever, Jan 29, 2006

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.