git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Mike Ralphson" <mike.ralphson@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>, "Jeff King" <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: A note from the interim Git maintainer
Date: Fri, 26 Sep 2008 14:24:31 +0100	[thread overview]
Message-ID: <e2b179460809260624n4b329345q3610069af5af75c2@mail.gmail.com> (raw)
In-Reply-To: <20080924154632.GR3669@spearce.org>

2008/9/24 Shawn O. Pearce <spearce@spearce.org>:
> 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

  reply	other threads:[~2008-09-26 13:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 15:46 A note from the interim Git maintainer Shawn O. Pearce
2008-09-26 13:24 ` Mike Ralphson [this message]
2008-09-26 22:54   ` Jeff King
2008-09-29  7:51     ` Mike Ralphson
2008-10-01  7:16       ` obscure platform autobuilders Jeff King
2008-10-01 10:46         ` Mike Ralphson
2008-10-01 15:37           ` Jeff King
  -- strict thread matches above, loose matches on Subject: below --
2007-10-16  5:54 A note from the interim Git maintainer Shawn O. Pearce
2007-10-17  6:31 ` Eric Wong
2007-10-17  7:13   ` Shawn O. Pearce
2007-10-18  3:03     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e2b179460809260624n4b329345q3610069af5af75c2@mail.gmail.com \
    --to=mike.ralphson@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).