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

Re: [PATCH 7/7] Use a separate directory for patches under each branch subdir

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
Nov 30, 2005, 22:32 UTC
Message-ID
<b0943d9e0511301432m10b25887r@mail.gmail.com>
In-Reply-To
<438E2797.2020205@citi.umich.edu>
On 30/11/05, Chuck Lever <cel@citi.umich.edu> wrote:
Show 7 quoted lines
> Catalin Marinas wrote:
> > This patch doesn't fix the already created branches. It would be
> > useful to upgrade the branch structure automatically if the patches
> > directory is not found.
>
> the reason i didn't do that is because i wanted to allow older versions
> of StGIT to continue to work on existing repositories.
You are right.
> what if i added a migration tool to allow a user to switch back and forth?

A separate stg command for this would be useful. Anyway since the repository structure might change again in the future, I think it would be better to have a version string saved somewhere in .git/patches/version for reference.

-- Catalin

Previous: Chuck LeverNext: Chuck Lever
Message 14 of 16 in “[PATCH 0/7]”
  1. 0/7 Chuck Lever, Nov 29, 2005
  2. 1/7 Make "stg export" save the base commit in the output directoryChuck Lever, Nov 29, 2005
  3. Catalin MarinasNov 30, 2005
  4. 2/7 Use git-rev-parse to find the local GIT repositoryChuck Lever, Nov 29, 2005
  5. 3/7 Align branch descriptions in output of "stg branch -l"Chuck Lever, Nov 29, 2005
  6. 4/7 "stg series" option to show patch summary descriptionsChuck Lever, Nov 29, 2005
  7. 5/7 Add facility to print short list of patches around 'top'Chuck Lever, Nov 29, 2005
  8. 6/7 Add a "--clone" option to "stg branch"Chuck Lever, Nov 29, 2005
  9. Catalin MarinasDec 1, 2005
  10. Chuck LeverDec 1, 2005
  11. 7/7 Use a separate directory for patches under each branch subdirChuck Lever, Nov 29, 2005
  12. Catalin MarinasNov 30, 2005
  13. Chuck LeverNov 30, 2005
  14. Catalin MarinasNov 30, 2005
  15. Chuck LeverDec 1, 2005
  16. Catalin MarinasNov 30, 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.