Starting 1.5.3 stabilization cycle

Starting 1.5.3 stabilization cycle

[Junio C Hamano]

I tagged the tip of 'master' as 1.5.3-rc0; in addition to the
topics described in the latest "What's in", most of the topics
that have been cooking in 'next' are there.  The time some of
them have spent before going to 'master' might be shorter than
usual and there are a handful patches that I took directly to
'master', but the tip of 'master' should be as solid as usual.

There probably could be a few bits that we have already seen and
was reviewed on the list that deserve to be in v1.5.3 (the only
ones I have in mind right now are a few gitweb ones), but other
than that, I think this is pretty much it, modulo bugfixes.

Oh, by the way, a maintenance release 1.5.2.3 is also out.

----------------------------------------------------------------

GIT v1.5.3 Release Notes (draft as of -rc0)
========================

Updates since v1.5.2
--------------------

* The commit walkers other than http are officially deprecated
  (but still supported).

* The submodule support has Porcelain layer now.

* An initial interation of Porcelain level superproject support
  started to take shape.

* Thee are a handful pack-objects changes to help you cope better with
  repositories with pathologically large blobs in them.

* For people who need to import from Perforce, a front-end for
  fast-import is in contrib/fast-import/ now.

* Comes with git-gui 0.8.0.

* Comes with updated gitk.

* New commands and options.

  - "git stash" allows you to quickly save away your work in
    progress and replay it later on an updated state.

  - "git rebase" learned an "interactive" mode.

  - "git fsck" can save its findings in lost-found, without a
    separate invocation of "git lost-found" command.

  - GIT_WORK_TREE environment variable can be used together with
    GIT_DIR to work in a subdirectory of a working tree that is
    not located at "$GIT_DIR/..".

  - "git log" learned a new option '--follow', to follow
    renaming history of a single file.

  - "git-filter-branch" is a reborn cg-admin-rewritehist.

  - "git-cvsserver" learned new options (--base-path, --export-all,
    --strict-paths) inspired by git-daemon.

  - "git-submodule" command helps you manage the projects from
    the superproject that contain them.

  - In addition to core.compression configuration option,
    core.loosecompression and pack.compression options can
    independently tweak zlib compression levels used for loose
    and packed objects.

  - "git-ls-tree -l" shows size of blobs pointed at by the
    tree entries, similar to "/bin/ls -l".

  - "git-rev-list" learned --regexp-ignore-case and
    --extended-regexp options to tweak its matching logic used
    for --grep fitering.

  - "git-describe --contains" is a handier way to call more
    obscure command "git-name-rev --tags".

  - "git gc --aggressive" tells the command to spend more cycles
    to optimize the repository harder.

  - "git repack" can be told to split resulting packs to avoid
    exceeding limit specified with "--max-pack-size".

  - "git fsck" gained --verbose option.  This is really really
    verbose but it might help you identify exact commit that is
    corrupt in your repository.

  - "git format-patch" learned --numbered-files option.  This
    may be useful for MH users.

  - "git format-patch" learned format.subjectprefix
    configuration variable, which serves the same purpose as the
    existing --subject-prefix option.

  - "git tag -n -l" shows tag annotations while listing tags.

  - "git cvsimport" can optionally use the separate-remote layout.

  - "git blame" can be told to see through commits that changes
    whitespaces and indentation levels with "-w" option.

  - "git send-email" can be told not to thread the messages when
    sending out more than one patches.

  - "git config" learned NUL terminated output format via -z to
    help scripts.

  - "git init -q" makes it quieter.

* Updated behavior of existing commands.

  - "git svn dcommit" retains local merge information.

  - "git config" to set values also honor type flags like --bool
    and --int.

  - core.quotepath configuration can be used to make textual git
    output to emit most of the characters in the path literally.

  - "git mergetool" chooses its backend more wisely, taking
    notice of its environment such as use of X, Gnome/KDE, etc.

  - "gitweb" shows merge commits a lot nicer than before.  The
    default view uses more compact --cc format, while the UI
    allows to choose normal diff with any parent.

  - snapshot files "gitweb" creates from a repository at
    $path/$project/.git are more useful.  We use $project part
    in the filename, which we used to discard.

  - "git cvsimort" creates lightweight tag; there is not any
    interesting information we can record in an annotated tag,
    and the handcrafted ones the old code created was not
    properly formed anyway.

  - "git-push" pretends that you immediately fetched back from
    the remote by updating corresponding remote tracking
    branches if you have any.

  - The diffstat given after a merge (or a pull) honors the
    color.diff configuration.

  - "git-apply --whitespace=strip" removes blank lines added at
    the end of the file.

  - "git-fetch" over git native protocols with -v shows connection
    status, and the IP address of the other end, to help
    diagnosing problems.

  - We used to have core.legacyheaders configuration, when
    set to false, allowed git to write loose objects in a format
    that mimicks the format used by objects stored in packs.  It
    turns out that this was not so useful.  Although we will
    continue to read objects written in that format, we do not
    honor that configuration anymore and create loose objects in
    the legacy/traditional format.

  - "--find-copies-harder" option to diff family can now be
    spelled as "-C -C" for brevity.

  - "git-mailsplit" (hence "git-am") can read from Maildir
    formatted mailboxes.

  - "git-cvsserver" does not barf upon seeing "cvs login"
    request.

  - "pack-objects" honors "delta" attribute set in
    .gitattributes.  It does not attempt to deltify blobs that
    come from paths with delta attribute set to false.

  - new-workdir script (in contrib) can now be used with a bare
    repository.

  - "git-mergetool" learned to use gvimdiff.

  - "gitview" (in contrib) has a better blame interface.

  - "git log" and friends did not handle a commit log message
    that is larger than 16kB; they do now.

  - "--pretty=oneline" output format for "git log" and friends
    deals with "malformed" commit log messages that have more
    than one lines in the first paragraph better.  We used to
    show the first line, cutting the title at mid-sentence; we
    concatenate them into a single line and treat the result as
    "oneline".

* Builds

  - old-style function definitions (most notably, a function
    without parameter defined with "func()", not "func(void)")
    have been eradicated.

* Performance Tweaks

  - git-pack-objects avoids re-deltification cost by caching
    small enough delta results it creates while looking for the
    best delta candidates.

  - diff-delta code that is used for packing has been improved
    to work better on big files.

  - when there are more than one pack files in the repository,
    the runtime used to try finding an object always from the
    newest packfile; it now tries the same packfile as we found
    the object requested the last time, which exploits the
    locality of references.

  - verifying pack contents done by "git fsck --full" got boost
    by carefully choosing the order to verify objects in them.


Fixes since v1.5.2
------------------

All of the fixes in v1.5.2 maintenance series are included in
this release, unless otherwise noted.

* Bugfixes

  - "gitweb" had trouble handling non UTF-8 text with older
    Encode.pm Perl module.

Re: Starting 1.5.3 stabilization cycle

[Frank Lichtenheld]

On Tue, Jul 03, 2007 at 12:29:32AM -0700, Junio C Hamano wrote:
> GIT v1.5.3 Release Notes (draft as of -rc0)
> ========================
> 
> Updates since v1.5.2
> --------------------
> 
> * The commit walkers other than http are officially deprecated
>   (but still supported).
> 
> * The submodule support has Porcelain layer now.
> 
> * An initial interation of Porcelain level superproject support
>   started to take shape.

Should that be "iteration"?

> * Thee are a handful pack-objects changes to help you cope better with
>   repositories with pathologically large blobs in them.

"There"?

> * Updated behavior of existing commands.
> 
>   - "git svn dcommit" retains local merge information.
> 
>   - "git config" to set values also honor type flags like --bool
>     and --int.

"honors"

>   - "git cvsimort" creates lightweight tag; there is not any
>     interesting information we can record in an annotated tag,
>     and the handcrafted ones the old code created was not
>     properly formed anyway.

"lightweight tags"

Gruesse,
-- 
Frank Lichtenheld <frank@lichtenheld.de>
www: http://www.djpig.de/

Re: Starting 1.5.3 stabilization cycle

[Peter Baumann]

On Tue, Jul 03, 2007 at 12:29:32AM -0700, Junio C Hamano wrote:
> I tagged the tip of 'master' as 1.5.3-rc0; in addition to the
> topics described in the latest "What's in", most of the topics
> that have been cooking in 'next' are there.  The time some of
> them have spent before going to 'master' might be shorter than
> usual and there are a handful patches that I took directly to
> 'master', but the tip of 'master' should be as solid as usual.
> 
> There probably could be a few bits that we have already seen and
> was reviewed on the list that deserve to be in v1.5.3 (the only
> ones I have in mind right now are a few gitweb ones), but other
> than that, I think this is pretty much it, modulo bugfixes.
> 
> Oh, by the way, a maintenance release 1.5.2.3 is also out.
> 
> ----------------------------------------------------------------
> 
> GIT v1.5.3 Release Notes (draft as of -rc0)
> ========================
> 
> Updates since v1.5.2
> --------------------
> 
> * The commit walkers other than http are officially deprecated
>   (but still supported).

/
|> 
|> * The submodule support has Porcelain layer now.
|> 
|> * An initial interation of Porcelain level superproject support
                ^^^^^^^^^^ typo
|>   started to take shape.
\
  Duplicated?

> 
> * Thee are a handful pack-objects changes to help you cope better with
>   repositories with pathologically large blobs in them.
> 
> * For people who need to import from Perforce, a front-end for
>   fast-import is in contrib/fast-import/ now.
> 
> * Comes with git-gui 0.8.0.
> 
> * Comes with updated gitk.
> 
> * New commands and options.
> 
>   - "git stash" allows you to quickly save away your work in
>     progress and replay it later on an updated state.
> 
>   - "git rebase" learned an "interactive" mode.

Short describtion missing?

	This is meant for reordering the commits, merge several commits into
	one or even remove some of them.

> 
>   - "git fsck" can save its findings in lost-found, without a
>     separate invocation of "git lost-found" command.
> 
>   - GIT_WORK_TREE environment variable can be used together with
>     GIT_DIR to work in a subdirectory of a working tree that is
>     not located at "$GIT_DIR/..".
> 
>   - "git log" learned a new option '--follow', to follow
>     renaming history of a single file.
> 
>   - "git-filter-branch" is a reborn cg-admin-rewritehist.

Better mention what it is for, e.g:

	Lets you rewrite GIT revision history by applying custom filters on each revision.
	Those filters can modify each tree or information about each commit.

> 
>   - "git-cvsserver" learned new options (--base-path, --export-all,
>     --strict-paths) inspired by git-daemon.

[...]

>   - snapshot files "gitweb" creates from a repository at
>     $path/$project/.git are more useful.  We use $project part
>     in the filename, which we used to discard.
> 
>   - "git cvsimort" creates lightweight tag; there is not any
                ^- should be "cvsimport"
>     interesting information we can record in an annotated tag,
>     and the handcrafted ones the old code created was not
>     properly formed anyway.
> 
>   - "git-push" pretends that you immediately fetched back from
>     the remote by updating corresponding remote tracking
>     branches if you have any.
> 
>   - The diffstat given after a merge (or a pull) honors the
>     color.diff configuration.
> 
>   - "git-apply --whitespace=strip" removes blank lines added at
>     the end of the file.
> 
>   - "git-fetch" over git native protocols with -v shows connection
>     status, and the IP address of the other end, to help
>     diagnosing problems.
> 
>   - We used to have core.legacyheaders configuration, when
>     set to false, allowed git to write loose objects in a format
>     that mimicks the format used by objects stored in packs.  It
>     turns out that this was not so useful.  Although we will
>     continue to read objects written in that format, we do not
>     honor that configuration anymore and create loose objects in
>     the legacy/traditional format.
> 
>   - "--find-copies-harder" option to diff family can now be
>     spelled as "-C -C" for brevity.
> 
>   - "git-mailsplit" (hence "git-am") can read from Maildir
>     formatted mailboxes.
> 
>   - "git-cvsserver" does not barf upon seeing "cvs login"
>     request.
> 
>   - "pack-objects" honors "delta" attribute set in
>     .gitattributes.  It does not attempt to deltify blobs that
>     come from paths with delta attribute set to false.
> 
>   - new-workdir script (in contrib) can now be used with a bare
>     repository.
> 
>   - "git-mergetool" learned to use gvimdiff.
> 
>   - "gitview" (in contrib) has a better blame interface.
> 
>   - "git log" and friends did not handle a commit log message
>     that is larger than 16kB; they do now.
> 
>   - "--pretty=oneline" output format for "git log" and friends
>     deals with "malformed" commit log messages that have more
>     than one lines in the first paragraph better.  We used to
>     show the first line, cutting the title at mid-sentence; we
>     concatenate them into a single line and treat the result as
>     "oneline".
> 
> * Builds
> 
>   - old-style function definitions (most notably, a function
>     without parameter defined with "func()", not "func(void)")
>     have been eradicated.
> 
> * Performance Tweaks
> 
>   - git-pack-objects avoids re-deltification cost by caching
>     small enough delta results it creates while looking for the
>     best delta candidates.
> 
>   - diff-delta code that is used for packing has been improved
>     to work better on big files.
> 
>   - when there are more than one pack files in the repository,

I'm no native english speaker, but shouldn't this be

    - when there is more then one pack file in the repository,
                 ^^                    ^^^^
>     the runtime used to try finding an object always from the
>     newest packfile; it now tries the same packfile as we found
>     the object requested the last time, which exploits the
>     locality of references.
> 
>   - verifying pack contents done by "git fsck --full" got boost
>     by carefully choosing the order to verify objects in them.
> 
> 
> Fixes since v1.5.2
> ------------------
> 
> All of the fixes in v1.5.2 maintenance series are included in
> this release, unless otherwise noted.
> 
> * Bugfixes
> 
>   - "gitweb" had trouble handling non UTF-8 text with older
>     Encode.pm Perl module.
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: Starting 1.5.3 stabilization cycle

[Johannes Schindelin]

Hi,

On Tue, 3 Jul 2007, Peter Baumann wrote:

> On Tue, Jul 03, 2007 at 12:29:32AM -0700, Junio C Hamano wrote:
> 
> >   - "git rebase" learned an "interactive" mode.
> 
> Short describtion missing?

s/b/p/ ;-)

> 	This is meant for reordering the commits, merge several commits into
> 	one or even remove some of them.

Or even better:

	- "git rebase" learned an "interactive" mode, where you can pick 
	  and reorder the commits to be applied.

> >   - "git-filter-branch" is a reborn cg-admin-rewritehist.
> 
> Better mention what it is for, e.g:
> 
> 	Lets you rewrite GIT revision history by applying custom filters 
>	on each revision. Those filters can modify each tree or 
>	information about each commit.

I never liked that description. How about (shameless plug) the description 
from my last patch:

	git-filter-branch lets you rewrite the revision history of the 
	current branch, creating a new branch. You can specify a number of 
	filters to modify the commits, files and trees.

Ciao,
Dscho

Re: Starting 1.5.3 stabilization cycle

[Peter Baumann]

On Tue, Jul 03, 2007 at 07:27:54PM +0100, Johannes Schindelin wrote:

[... skipping an embarrassing part of the message :-) ...]

> > 	This is meant for reordering the commits, merge several commits into
> > 	one or even remove some of them.
> 
> Or even better:
> 
> 	- "git rebase" learned an "interactive" mode, where you can pick 
> 	  and reorder the commits to be applied.

Sounds nicer, but I would add that it is also possible to remove commits.

> > >   - "git-filter-branch" is a reborn cg-admin-rewritehist.
> > 
> > Better mention what it is for, e.g:
> > 
> > 	Lets you rewrite GIT revision history by applying custom filters 
> >	on each revision. Those filters can modify each tree or 
> >	information about each commit.
> 
> I never liked that description. How about (shameless plug) the description 
> >from my last patch:
> 
> 	git-filter-branch lets you rewrite the revision history of the 
> 	current branch, creating a new branch. You can specify a number of 
> 	filters to modify the commits, files and trees.

I find it a little distracting to mention the "new branch" in this short
description. I think this belongs into the manpage and not in a short
description for the release notes. But I agree that this sounds otherwise nicer.

-Peter