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

Re: StGIT: stgitformatversion vs. stgit.formatversion

From
Karl Hasselström <kha@treskal.com>
Date
Jun 3, 2007, 12:17 UTC
Message-ID
<20070603121718.GA6507@diana.vm.bytemark.co.uk>
In-Reply-To
<20070602191641.GB6992@nan92-1-81-57-214-146.fbx.proxad.net>
On 2007-06-02 21:16:41 +0200, Yann Dirson wrote:
> What about using branch.*.stgit.formatversion to store the version,
> to be consistent with other stgit-specific per-branch settings ?

Good idea. But we should probably fall back to stgitformatversion (or better, upgrade from it) to be nice to those running Catalin's master.

It happens a bit too often that we find problems with patches only after Catalin has published them on "master". (At least that seems to be the case with patches coming from me!) Maybe a "pu" branch (maintained either by Catalin or someone else) would be a good way to smoke them out before they're written in stone and distributed to lots of people.

If the stgitformatversion patch had been on such a branch, we could just have edited it and not have to worry about upgrading old configs (aside from posting a mail on how to upgrade manually).

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Yann DirsonNext: Catalin Marinas
Message 2 of 5 in “StGIT: stgitformatversion vs. stgit.formatversion”
  1. Yann DirsonJun 2, 2007
  2. Karl HasselströmJun 3, 2007
  3. Catalin MarinasJun 4, 2007
  4. Catalin MarinasJun 7, 2007
  5. Karl HasselströmJun 10, 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.