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

Re: [StGIT RFC PATCH] Don't use refs/bases/<branchname>

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
May 1, 2007, 08:37 UTC
Message-ID
<b0943d9e0705010137q4a35f818m7dbbc9d2e77e2fcf@mail.gmail.com>
In-Reply-To
<20070429220832.5832.251.stgit@yoghurt>
On 30/04/07, Karl Hasselström <kha@treskal.com> wrote:
> It's silly to save the stack base in a ref when it can trivially be
> computed from the bottommost applied patch, if any. (If there are no
> applied patches, it's simply equal to HEAD.)

The reason I initially had the base ref was to see what's on top of the stack when using gitk. I later added refs/patches/<branch>/... which are shown by gitk and the base ref would be redundant.

I'm OK with this patch as long as tools like qgit don't rely on this ref.
-- 
Catalin
Previous: Karl HasselströmNext: Marco Costalba
Message 2 of 8 in “Don't use refs/bases/<branchname>”
  1. Don't use refs/bases/<branchname>Karl Hasselström, Apr 29, 2007
  2. Catalin MarinasMay 1, 2007
  3. Marco CostalbaMay 1, 2007
  4. Karl HasselströmMay 1, 2007
  5. Marco CostalbaMay 1, 2007
  6. Karl HasselströmMay 2, 2007
  7. Marco CostalbaMay 2, 2007
  8. Karl HasselströmMay 2, 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.