[Git-commits] core configuration files of grml branch, mru/no-persistent-undo, updated. v0.3.87-1-g7fa17ed

[git repository hosting]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "core configuration files of grml".

The branch, mru/no-persistent-undo has been updated
  discards  2967f2c5e7a85fd5d4d688dab36263faa576249d (commit)
       via  7fa17edeb4de85d2ff9859ccef8b086b066a2c5f (commit)
       via  5c9a156904512512cf572f3b29ede9c30a3bf9b9 (commit)
       via  fff04ca7d720585b70fd52fe820dc08a399e46c0 (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (2967f2c5e7a85fd5d4d688dab36263faa576249d)
            \
             N -- N -- N (7fa17edeb4de85d2ff9859ccef8b086b066a2c5f)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 7fa17edeb4de85d2ff9859ccef8b086b066a2c5f
Author: Ulrich Dangel <uli at spamt.net>
Date:   Wed Dec 22 11:22:18 2010 +0100

    Remove persistent undo for vim
    
    After some discussion with ft and mika we decided that persistent undo
    should be part of our default configuration as it changes existing
    workflows.

commit 5c9a156904512512cf572f3b29ede9c30a3bf9b9
Author: Michael Prokop <mika at grml.org>
Date:   Fri Dec 17 12:36:58 2010 +0100

    Release new version 0.3.87.

commit fff04ca7d720585b70fd52fe820dc08a399e46c0
Author: Frank Terbeck <ft at grml.org>
Date:   Wed Dec 8 12:59:54 2010 +0100

    Adding a kill to slash binding to alt-backspace
    
    As requested by mika, mrud and kafux.
    
    I'm binding the widget to "M-C-h" and "M-C-?" because those are common
    codes send by the backspace key in various terminals (and sometimes
    terminfo lies about it).

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

Summary of changes:
 debian/changelog |    7 +++++++
 etc/vim/vimrc    |    8 ++++++--
 etc/zsh/zshrc    |    4 ++++
 3 files changed, 17 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
core configuration files of grml