newsvc-dwim - News: vc-dwim-1.3 released [stable]

 
 
Latest News
vc-dwim-1.10 released [stable] posted by meyering, Fri 16 Oct 2020 06:34:04 AM UTC
vc-dwim-1.8 released [stable] posted by meyering, Sat 14 Jan 2017 05:20:45 PM UTC
vc-dwim-1.6 released [stable] posted by meyering, Fri 23 Dec 2011 11:39:40 AM UTC
vc-dwim-1.5 released [stable] posted by meyering, Fri 20 May 2011 06:53:42 AM UTC
vc-dwim-1.4 released [stable] posted by meyering, Fri 18 Mar 2011 10:11:13 AM UTC

vc-dwim-1.3 released [stable]

Item posted by Jim Meyering <meyering> on Sat 06 Nov 2010 11:53:53 AM UTC.


This release includes the bug fix mentioned below and a
portability tweak, but not much else.

In case you're wondering what this package does, see

  http://www.gnu.org/software/vc-dwim/

Very briefly, there are two tools:
   vc-dwim is a version-control-agnostic ChangeLog diff and commit tool.
   vc-chlog is a helper tool for writing GNU-style ChangeLog entries.


Here are the compressed sources:
  ftp://ftp.gnu.org/gnu/vc-dwim/vc-dwim-1.3.tar.gz   (340KB)
  ftp://ftp.gnu.org/gnu/vc-dwim/vc-dwim-1.3.tar.xz   (260KB)

Here are the GPG detached signatures[*]:
  ftp://ftp.gnu.org/gnu/vc-dwim/vc-dwim-1.3.tar.gz.sig
  ftp://ftp.gnu.org/gnu/vc-dwim/vc-dwim-1.3.tar.xz.sig

To reduce load on the main server, use a mirror listed at:
  http://www.gnu.org/order/ftp.html

[*] You can use either of the above signature files to verify that
the corresponding file (without the .sig suffix) is intact.  First,
be sure to download both the .sig file and the corresponding tarball.
Then, run a command like this:

  gpg --verify vc-dwim-1.3.tar.gz.sig

If that command fails because you don't have the required public key,
then run this command to import it:

  gpg --keyserver keys.gnupg.net --recv-keys 000BEEEE

and rerun the `gpg --verify' command.

This release was bootstrapped with the following tools:
  Autoconf 2.68.3-de12b
  Automake 1.11a
  Gnulib v0.0-4415-g4baf5c1

./NEWS

* Noteworthy changes in release 1.3 (2010-11-06) [stable]

  vc-dwim now commits the symlink'd ChangeLog *after* the primary commit,
  not before it.  This is more useful because the primary one is far more
  likely to fail, e.g., due to a commit hook.  Now, when that happens, the
  ChangeLog delta is left uncommitted, as you probably require, so that you
  can run vc-dwim after correcting the problem with the primary commit.


 

Back to the top

Powered by Savane 3.13-4448.
Corresponding source code