From: Andreas Gruenbacher <agruen@gnu.org>
To: info-gnu@gnu.org
Cc: git@vger.kernel.org
Subject: GNU patch: 2.6.1 release (mostly bugfixes)
Date: Wed, 30 Dec 2009 17:30:21 +0100 [thread overview]
Message-ID: <200912301730.21746.agruen@gnu.org> (raw)
Some glitches in release 2.6 of GNU patch made a new release 2.6.1 necessary,
available from:
ftp://ftp.gnu.org/gnu/patch/
The previous release was on 13 November. NEWS since then:
* Support for diff3(1) style merges which show the old, original, and new
lines of a conflict has been added (--merge=diff3). The default still is
the merge(1) format (--merge or --merge=merge).
* Bug and portability fixes.
The source code repository, a bug-patch@gnu.org mailing list archive, and the
project's bug tracker are available at:
http://savannah.gnu.org/projects/patch
Please email bugs or suggestions to <bug-patch@gnu.org>. Check the bug
tracker for a list of known issues.
Thanks,
Andreas
reply other threads:[~2009-12-30 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200912301730.21746.agruen@gnu.org \
--to=agruen@gnu.org \
--cc=git@vger.kernel.org \
--cc=info-gnu@gnu.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).