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

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

From
MCMarco Costalba <mcostalba@gmail.com>
Date
May 2, 2007, 11:17 UTC
Message-ID
<e5bfff550705020417h14f6297fu957eb64e58119770@mail.gmail.com>
In-Reply-To
<20070502065054.GA9919@diana.vm.bytemark.co.uk>
On 5/2/07, Karl Hasselström <kha@treskal.com> wrote:
Show 5 quoted lines
>
> It's not near the top of my kill list by any stretch of the
> imagination, so no need to worry. And even if it were, Catalin would
> certainly stand as a wall of sanity between qgit and my chain saw. :-)
>

Currently I check for the existence of <git dir>/patches directory as a quick exit in case a repository does NOT have a StGIT repo on it (the common case).

This avoids a costly and 99% of cases not needed 'stg <something>' call.

I ask if it will be still a safe check in the long period or it is better to change the check to something else (as existence of <git dir>/refs/patches) instead ?

Thanks Marco

Previous: Karl HasselströmNext: Karl Hasselström
Message 7 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.