From: Shawn O. Pearce <spearce@...>
Subject: A note from the interim Git maintainer
 [1]Date: Oct 16, 1:54 am 2007

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 [2]
  git:     git://repo.or.cz/git/spearce.git
           http://repo.or.cz/r/git/spearce.git [3]

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.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org [4]
More majordomo info at  http://vger.kernel.org/majordomo-info.html [5]


From: Eric Wong <normalperson@...>
Subject: Re: A note from the interim Git maintainer
 [5]Date: Oct 17, 2:31 am 2007

"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 [6]  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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org [7]
More majordomo info at  http://vger.kernel.org/majordomo-info.html [8]


From: Shawn O. Pearce <spearce@...>
Subject: Re: A note from the interim Git maintainer
 [8]Date: Oct 17, 3:13 am 2007

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 [9]  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.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org [10]
More majordomo info at  http://vger.kernel.org/majordomo-info.html [11]

From: Shawn O. Pearce <spearce@...>
Subject: What's in git/spearce.git (stable)
 [11]Date: Oct 16, 1:56 am 2007

* The 'maint' branch has these fixes since the last announcement.
  Please note that the last announcement was from Junio and was
  for the 1.5.3.4 release.

Frank Lichtenheld (1):
  git-config: don't silently ignore options after --list

Gerrit Pape (1):
  git-config: handle --file option with relative pathname properly

Jean-Luc Herren (2):
  git add -i: Fix parsing of abbreviated hunk headers
  git add -i: Remove unused variables

Johannes Schindelin (2):
  clear_commit_marks(): avoid deep recursion
  rebase -i: use diff plumbing instead of porcelain

Linus Torvalds (2):
  Fix embarrassing "git log --follow" bug
  Clean up "git log" format with DIFF_FORMAT_NO_OUTPUT

Mathias Megyei (1):
  Do not remove distributed configure script

Michele Ballabio (2):
  git-reflog: document --verbose
  git-archive: document --exec

Shawn O. Pearce (1):
  Whip post 1.5.3.4 maintenance series into shape.


* The 'master' branch has these since the last announcement
  in addition to the above.

Alex Riesen (1):
  fix t5403-post-checkout-hook.sh: built-in test in dash does not
      have "=="

Brandon Casey (2):
  git-gc: by default use safer "-A" option to repack when not
      --prune'ing
  git-gc --auto: simplify "repack" command line building

Brian Ewins (2):
  Add a --dry-run option to git-send-pack.
  Add a --dry-run option to git-push.

Eygene Ryabinkin (1):
  git-svn: respect Subversion's [auth] section configuration values

Frederick Akalin (1):
  gtksourceview2 support for gitview

Jeff King (1):
  git-rebase: document suppression of duplicate commits

Jeff Muizelaar (1):
  fix contrib/hooks/post-receive-email hooks.recipients error message

Johannes Schindelin (2):
  Support cvs via git-shell
  cvsexportcommit: get rid of temporary directory

Josh England (1):
  Minor usage update in setgitperms.perl

Kristof Provost (1):
  makefile: Add a cscope target

Marius Storm-Olsen (1):
  Add 'git-p4 commit' as an alias for 'git-p4 submit'

Michael Gebetsroither (1):
  hg-to-git speedup through selectable repack intervals

Michael Olson (1):
  Documentation/git-tag.txt: Document how to backdate tags

Michael W. Olson (1):
  git-rebase--interactive.sh: Quote arguments to test

Mike Dalessio (2):
  instaweb: allow for use of auto-generated scripts
  instaweb: support for Ruby's WEBrick server

Pierre Habouzit (1):
  Fix in-place editing functions in convert.c

Ralf Wildenhues (6):
  manual: Fix or remove em dashes.
  Fix some typos, punctuation, missing words, minor markup.
  Fix wording in push definition.
  manual: Fix example finding commits referencing given content.
  manual: add some markup.
  manual: use 'URL' instead of 'url'.

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org [12]
More majordomo info at  http://vger.kernel.org/majordomo-info.html [13]

From: Shawn O. Pearce <spearce@...>
Subject: What's cooking in git/spearce.git (topics)
 [13]Date: Oct 16, 2:04 am 2007

Here are the topics that have been cooking.  Commits prefixed
with '-' are only in 'pu' while commits prefixed with '+' are
in 'next'.  The topics list the commits in reverse chronological
order.

I know there are a number of other topics that I don't have in my
tree yet (bisect improvements, push refspec matching improvements,
option parser).  I plan on loading those into 'pu' tomorrow.
In the meantime we have this in next.


* db/fetch-pack (Thu Oct 11 01:47:55 2007 +0100) 58 commits
 + fetch: if not fetching from default remote, ignore default merge
 + Support 'push --dry-run' for http transport
 + Support 'push --dry-run' for rsync transport
 + Fix 'push --all branch...' error handling
 + Fix compilation when NO_CURL is defined
 + Added a test for fetching remote tags when there is not tags.
 + Fix a crash in ls-remote when refspec expands into nothing
 + Remove duplicate ref matches in fetch
 ... and many more ...

 The above commits are all new since Junio's last published next.
 About half of them fix known bugs in the builtin-fetch series.
 If you are running next, you want these fixes.

 I'm actually really happy with this series, but given the set of
 bugs that the above commits had to fix I think it needs to cook
 more in next before the topic can safely can graduate into master.

* jc/am-quiet (Mon Oct 1 00:27:51 2007 -0700) 2 commits
 + git-am: fix typo in the previous one.
 + git-am: make the output quieter.

 I'm also really happy with this change.  If nobody objects I may
 move it over to master later this week.


* lt/diff-rename (Tue Oct 2 19:28:19 2007 -0700) 1 commit
 + optimize diffcore-delta by sorting hash entries.

* kh/commit (Mon Sep 17 20:06:47 2007 -0400) 4 commits
 + Export rerere() and launch_editor().
 + Introduce entry point add_interactive and add_files_to_cache
 + Enable wt-status to run against non-standard index file.
 + Enable wt-status output to a given FILE pointer.

* js/stash-create (Mon Jul 9 00:51:23 2007 -0700) 2 commits
 + rebase: allow starting from a dirty tree.
 + stash: implement "stash create"

I inherited the above three topics from Junio.  I haven't had a
chance to really look at these yet myself to understand what their
status is and how ready they are for master (or not ready as the
case may be).
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org [14]
More majordomo info at  http://vger.kernel.org/majordomo-info.html [15]