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

Re: Moving initialization of log_all_ref_updates

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jan 7, 2007, 10:05 UTC
Message-ID
<20070107100559.GC10351@spearce.org>
In-Reply-To
<7v4pr32mcn.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
Show 7 quoted lines
> "Shawn O. Pearce" <spearce@spearce.org> writes:
> 
> > Do we want to consider having init-db/clone set core.bare based on
> > what they are being asked to do?
> 
> Here is what I have as a follow-up patch to the one you are
> responding to.
I like.  :-)
Worthy of 1.5.0 me thinks.
-- 
Shawn.
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 5 in “Moving initialization of log_all_ref_updates”
  1. Junio C HamanoJan 7, 2007
  2. Shawn O. PearceJan 7, 2007
  3. Junio C HamanoJan 7, 2007
  4. Shawn O. PearceJan 7, 2007
  5. git-fetch: allow updating the current branch in a bare repository.Junio C Hamano, Jan 7, 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.