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

Re: A note from the interim Git maintainer

From
Mike Ralphson <mike.ralphson@gmail.com>
Date
Sep 26, 2008, 13:24 UTC
Message-ID
<e2b179460809260624n4b329345q3610069af5af75c2@mail.gmail.com>
In-Reply-To
<20080924154632.GR3669@spearce.org>
2008/9/24 Shawn O. Pearce <spearce@spearce.org>:
Show 15 quoted lines
> My tree is being published here:
>
>  git:    git://repo.or.cz/git/spearce.git
>                  repo.or.cz/srv/git/git/spearce.git
>          http://repo.or.cz/r/git/spearce.git
>
>  gitweb: http://repo.or.cz/w/git/spearce.git
>
> The usual maint/master/next/pu stuff applies.  I'm basically just
> picking up from where Junio left off.
>
> I would appreciate it if anyone who normally tracks Junio's "next"
> or "master" branch for their production work can switch over to my
> next (or master) branch for the next few weeks.  Something about
> many eyeballs and fewer bugs.

Now there are new commits in this tree, Gitbuild [http://repo.or.cz/w/git/gitbuild.git] has spearce/master, spearce/maint and spearce/next branches and I'm currently running my automated AIX test builds on these branches and pushing the relevant tags along.

Jeff, if you want to switch your BSD builds to Shawn's tree too, I made and pushed a tiny change to the gitbuild.sh script to allow for the spearce/{branch} format becoming spearce_{branch} in the tag names.

Cheers, Mike
Previous: Shawn O. PearceNext: Jeff King
Message 2 of 7 in “A note from the interim Git maintainer”
  1. Shawn O. PearceSep 24, 2008
  2. Mike RalphsonSep 26, 2008
  3. Jeff KingSep 26, 2008
  4. Mike RalphsonSep 29, 2008
  5. obscure platform autobuildersJeff King, Oct 1, 2008
  6. Mike RalphsonOct 1, 2008
  7. Jeff KingOct 1, 2008

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.