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 rel...
[ message continues ]

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

-

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

-

Exactly, it was late :)
--

Eric Wong

-