util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sami Kerola <kerolasa@iki.fi>
To: util-linux@vger.kernel.org
Cc: kerolasa@iki.fi
Subject: [PATCH 0/5] pull: release preparations, umount.8 and vipw fix
Date: Sat,  4 Aug 2012 09:33:35 +0200	[thread overview]
Message-ID: <1344065620-17480-1-git-send-email-kerolasa@iki.fi> (raw)

Hello,

The most of the following patches are preparations to final release.

Third patch will add sys-utils/umount.8 manual, which is almost
identical copy in comparison to old manual.  The big difference is that
new manual has long options.

The vipw change is a bug fix to a corner case bug that was discussed in
the mail list.  Preliminary tests on my computer gave feeling the fix
works, but it would be good to get more vipw testing with various
editors and configration combinations.

The following changes since commit 91f98496f3901ea68853745edac67e3288a3886d:

  docs: update tests docs (2012-08-03 21:33:32 +0200)

are available in the git repository at:

  git://github.com/kerolasa/lelux-utiliteetit.git 2012wk31

for you to fetch changes up to 67efed9623ce27f2ee582c32eda09946eb4eb1a8:

  vipw: make vim writebackup mode work (2012-08-04 09:05:47 +0200)

----------------------------------------------------------------
Sami Kerola (5):
      docs: ftp server does no longer support util-linux-ng
      docs: update TODO
      docs: add sys-utils/umount.8 manual page
      build-sys: add files make check generates in gitignore
      vipw: make vim writebackup mode work

 .gitignore                                |   4 +
 Documentation/TODO                        |   9 --
 Documentation/releases/v2.13-ReleaseNotes |   2 +-
 Documentation/releases/v2.14-ReleaseNotes |  10 +-
 Documentation/releases/v2.15-ReleaseNotes |  10 +-
 Documentation/releases/v2.16-ReleaseNotes |   6 +-
 Documentation/releases/v2.17-ReleaseNotes |  12 +-
 Documentation/releases/v2.18-ReleaseNotes |  12 +-
 NEWS                                      |  42 +++----
 login-utils/vipw.c                        |  12 ++
 sys-utils/Makemodule.am                   |   2 +-
 sys-utils/umount.8                        | 175 ++++++++++++++++++++++++++++++
 12 files changed, 239 insertions(+), 57 deletions(-)
 create mode 100644 sys-utils/umount.8



             reply	other threads:[~2012-08-04  7:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-04  7:33 Sami Kerola [this message]
2012-08-04  7:33 ` [PATCH 1/5] docs: ftp server does no longer support util-linux-ng Sami Kerola
2012-08-04  7:33 ` [PATCH 2/5] docs: update TODO Sami Kerola
2012-08-04  7:33 ` [PATCH 3/5] docs: add sys-utils/umount.8 manual page Sami Kerola
2012-08-04  7:33 ` [PATCH 4/5] build-sys: add files make check generates in gitignore Sami Kerola
2012-08-04  7:33 ` [PATCH 5/5] vipw: make vim writebackup mode work Sami Kerola
2012-08-06  6:14   ` Bernhard Voelker
2012-08-06  7:30     ` Sami Kerola
2012-08-06  8:28       ` Bernhard Voelker
2012-08-06 13:40 ` [PATCH 0/5] pull: release preparations, umount.8 and vipw fix Karel Zak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1344065620-17480-1-git-send-email-kerolasa@iki.fi \
    --to=kerolasa@iki.fi \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).