What's in master and pu (aka when will 1.0rc4 be out)

From: Junio C Hamano <junkio@cox.net>
Date: Nov 27, 2005, 10:56 UTC
Message-ID: <7vek52e4ve.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <7voe48gqg9.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <junkio@cox.net> writes:

Show 8 quoted lines

> This series is what I've been cooking for the past several days,
> partly based on patch from Martin Atukunda but with hopefully
> smaller impact.
>
> [PATCH 1/4] Repository format version check.
> [PATCH 2/4] Check repository format version in enter_repo().
> [PATCH 3/4] init-db: check template and repository format.
> [PATCH 4/4] setup_git_directory(): check repository format version.

And they are now in the master branch, along with a couple of bugfixes I received in the last couple of days. I've given them some testing and believe they are in good enough shape for 1.0 futureproofing. Bug reports with reproduction recipe and/or patch are most welcomed.

Cooking in the proposed updates branch is the 8-series "work from subdirectory" patch I posted yesterday, with some polishing based on suggestion from Linus. The ls-tree rework is not included at this point, neither is the git-sh-setup, both of which unfortunately have wider impact than I feel comfortable to swallow in one day.

I am hoping to base the next "maint" branch update, probably on Wednesday, on what is in "pu" tonight, with safer updates I will receive from the list (Documentation fixes and updates, and archimport updates from Eric and Martin are the candidates). That will be tagged as 1.0rc4 and hopefully be the last 1.0rc, which means no more major feature/semantics changes after that until 1.0 --- famous last words.

So I anticipate that many of the barebone Porcelain commands that insist on running from the toplevel will ship the way they are in 1.0. If you run "git grep git-sh-setup 'git*sh'", you will notice that most of them are whole-tree operations anyway, so not much is lost [*1*].

[Footnote]

*1* Bisecting only in a subdirectory might be an interesting thing to do, hunting down a bug in a subsystem, but usually a subsystem has at least two relevant subdirectories (source and include file trees) ;-).

I suspect that it would be trivial to convert whole-repository operations such as count-objects, prune, and repack to work from subdirectory, although the value of that is dubious.