A note from the interim Git maintainer

A note from the interim Git maintainer

[Shawn O. Pearce]

As most folks are probably now well aware, Junio has been offline
for about 11 days and may still be offline for a little while more.
Before he dropped offline Junio shared why he left on such a short
notice with both Dscho and myself, as it meant cancelling the
"git together" we were planning to have last weekend in San Jose.

I'm not going to get into the specific details as it is Junio's
business and not mine.  But I can say that my thoughts and prayers
to $DEITY are with him and his family at this time, and I don't
expect him to be rushing back to git work tomorrow.  However I'm
quite certain that Junio will return when he can.


Lars Hjemli has done a terrific job of stacking up patches from the
mailing list in his "q/*" branches, available for fetching directly
from his tree at [*1*].  I really want to thank Lars for stepping
up and doing this, as I think it has helped the community.

Unfortunately there were quite a few q/* branches, some of which
were not trivial to merge against the other topics that were already
pending in Junio's next.  Someone really needed to go through the
branches and merge them together into suitable maint, master and
next branches.


I've decided to step up and try to fill Junio's shoes.  To that end
I am publishing a maint, master, next (and soon) pu branch from a
new fork on repo.or.cz:

  gitweb:  http://repo.or.cz/w/git/spearce.git
  git:     git://repo.or.cz/git/spearce.git
           http://repo.or.cz/r/git/spearce.git

Traditional "What's in" messages will be sent in a minute.  I'm
going to try to apply the exact same policies that Junio applies
to these, so maint/master/next won't rewind, but pu may.

I based my branches on top of the last items published by Junio,
and am hoping that he will be open to pulling directly from these
before he starts working again.  Junio obviously has the option
not to pull from me, but if I do my job of interim maintainer well
I can probably talk him into it.  :)

I won't be publishing a tagged release from maint or master anytime
soon.  Primarily because I don't think its time to do that, and also
because I don't have a kernel.org account to upload the tarballs to.
If a month goes by without Junio, well, lets just see what happens.


I probably don't need to say this for the git regulars, but you
can start to track my published branches yourself with git-remote
if you are interested in testing and/or using these versions:

  $ git remote add -f spearce git://repo.or.cz/git/spearce.git
  $ git pull spearce master  ; # or next



*1* git://hjemli.net/pub/git/git

-- 
Shawn.

Re: A note from the interim Git maintainer

[Eric Wong]

"Shawn O. Pearce" <spearce@spearce.org> wrote:
> As most folks are probably now well aware, Junio has been offline
> for about 11 days and may still be offline for a little while more.
> Before he dropped offline Junio shared why he left on such a short
> notice with both Dscho and myself, as it meant cancelling the
> "git together" we were planning to have last weekend in San Jose.
> 
> I'm not going to get into the specific details as it is Junio's
> business and not mine.  But I can say that my thoughts and prayers
> to $DEITY are with him and his family at this time, and I don't
> expect him to be rushing back to git work tomorrow.  However I'm
> quite certain that Junio will return when he can.
> 
> I've decided to step up and try to fill Junio's shoes.  To that end
> I am publishing a maint, master, next (and soon) pu branch from a
> new fork on repo.or.cz:

Thanks for doing this, Shawn.  I hope Junio is doing OK.

I've pushed out Benoit's and Eygene's latest git-svn changes to master
on http://git.bogomips.org/git-svn.git  These changes are against
spearce/master.

I've amended Benoit's commit messages a bit and fixed one bug in
git svn propget (also amended).

Benoit Sigoure (5):
      git-svn: add a generic tree traversal to fetch SVN properties
      git-svn: implement git svn create-ignore
      git-svn: add git svn propget
      git-svn: add git svn proplist
      git-svn: simplify the handling of fatal errors

Eygene Ryabinkin (2):
      git-svn: respect Subversion's [auth] section configuration values
      git-svn: use "no warnings 'once'" to disable false-positives

-- 
Eric Wong

Re: A note from the interim Git maintainer

[Shawn O. Pearce]

Eric Wong <normalperson@yhbt.net> wrote:
> I've pushed out Benoit's and Eygene's latest git-svn changes to master
> on http://git.bogomips.org/git-svn.git  These changes are against
> spearce/master.
> 
> I've amended Benoit's commit messages a bit and fixed one bug in
> git svn propget (also amended).

Thanks.  I originally skipped over Benoit's changes as I hadn't see
anything from you on the subject.  But I have now cherry-picked them
from your bogomips git-svn tree into spearce/master.  Pushing it
out in a minute.
 
> Benoit Sigoure (5):
>       git-svn: add a generic tree traversal to fetch SVN properties
>       git-svn: implement git svn create-ignore
>       git-svn: add git svn propget
>       git-svn: add git svn proplist
>       git-svn: simplify the handling of fatal errors
> 
> Eygene Ryabinkin (2):
>       git-svn: respect Subversion's [auth] section configuration values
>       git-svn: use "no warnings 'once'" to disable false-positives

I apparently already had that first one from Eygene ("[auth]
section") in spearce/master; it went out last night.  Perhaps you
ran the shortlog above against Junio's tree and not mine?

The second one from Eygene ("no warnings once") I already had in
my master from the resend you had earlier made to the list with
your Ack and fixups.

-- 
Shawn.

Re: A note from the interim Git maintainer

[Eric Wong]

"Shawn O. Pearce" <spearce@spearce.org> wrote:
> Eric Wong <normalperson@yhbt.net> wrote:
> > Eygene Ryabinkin (2):
> >       git-svn: respect Subversion's [auth] section configuration values
> >       git-svn: use "no warnings 'once'" to disable false-positives
> 
> I apparently already had that first one from Eygene ("[auth]
> section") in spearce/master; it went out last night.  Perhaps you
> ran the shortlog above against Junio's tree and not mine?

Exactly, it was late :)

-- 
Eric Wong

A note from the interim Git maintainer

[Shawn O. Pearce]

As mentioned recently by Junio, Junio is away on family leave and
a much deserved vacation until ~Oct 6th.  Until he gets back I am
offering up my services as patch monkey to keep us moving along.

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.

Patches can be CC'd to me, or just sent to the list.  If I have
dropped something, please feel free to give me a gentle prod.

I know that I am quite behind on git-gui patches. I think I'm going
to spend the better part of today just on Git to get everything
caught up.

-- 
Shawn.

Re: A note from the interim Git maintainer

[Mike Ralphson]

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

Re: A note from the interim Git maintainer

[Jeff King]

On Fri, Sep 26, 2008 at 02:24:31PM +0100, Mike Ralphson wrote:

> 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.

Thanks, that's a good idea. I'm building Shawn's master (on my todo is
adding the other branches, too, but I need to tweak my script or tweak
gitbuild.sh and switch to it).

-Peff

Re: A note from the interim Git maintainer

[Mike Ralphson]

2008/9/26 Jeff King <peff@peff.net>
>
> On Fri, Sep 26, 2008 at 02:24:31PM +0100, Mike Ralphson wrote:
>
> > 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.
>
> Thanks, that's a good idea. I'm building Shawn's master (on my todo is
> adding the other branches, too, but I need to tweak my script or tweak
> gitbuild.sh and switch to it).

Feel free to push changes to gitbuild.sh, including getting rid of
anything which looks environment-specific.

Mike