From: "Max Bowsher" <maxb@ukf.net>
To: <cygwin-announce@cygwin.com>
Subject: Updated: patchutils 0.2.30-1
Date: Mon, 11 Oct 2004 00:32:00 -0000 [thread overview]
Message-ID: <002001c4af22$b50e0400$e6ec6f83@robinson.cam.ac.uk> (raw)
Patchutils (a suite of programs to perform useful manipulations on
unidiff-format patches) has been updated to new upstream version 0.2.30
(from 0.2.30pre1)
All previous Cygwin-local patches were merged upstream in this release.
The upstream ChangeLog is shown below:
2004-07-15 Tim Waugh <twaugh@redhat.com>
* configure.in: Version 0.2.30 (stable).
2004-07-15 Tim Waugh <twaugh@redhat.com>
* src/filterdiff.c (display_filename): Better padding for file
number.
2004-07-07 Tim Waugh <twaugh@redhat.com>
* src/diff.c (read_timezone): New function.
(read_timestamp): Use it. Suggested by Shawn Wagner, for parsing
another common traditional date format.
2004-07-03 Tim Waugh <twaugh@redhat.com>
* src/filterdiff.c (syntax): Explain --number-files a bit more.
* src/filterdiff.c (hunk_matches): Don't call file_matches()
unnecessarily.
2004-07-02 Tim Waugh <twaugh@redhat.com>
* src/filterdiff.c: New --number-files option for lsdiff/grepdiff.
* doc/patchutils.xml (lsdiff): Document it.
2004-05-19 Tim Waugh <twaugh@redhat.com>
* src/filterdiff.c (hunk_matches): Small correction.
2004-05-14 Tim Waugh <twaugh@redhat.com>
* doc/patchutils.xml (interdiff.1): Clarify requirement for
reference files being exactly the same.
2004-05-07 Tim Waugh <twaugh@redhat.com>
* doc/patchutils.xml: For grepdiff -n output format refer to the
lsdiff man page.
* src/filterdiff.c (main): Prevent -n being accepted by
filterdiff.
2004-05-06 Tim Waugh <twaugh@redhat.com>
* doc/patchutils.xml: Include --hunks/--lines/--files in lsdiff man
page.
* src/filterdiff.c: Fixed --help output.
* src/filterdiff.c: Added --files option, based on work by
Sérgio Monteiro Basto <sergiomb@netcabo.pt>.
* doc/patchutils.xml: Document it.
* tests/lsdiff12/run-test: Avoid using /dev/stdin, which is not
available on Cygwin set-ups.
* tests/flip*/run-test: Use /bin/echo instead of the shell builtin.
Patch from Max Bowsher <maxb@ukf.net>.
Max Bowsher.
--
To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page. This downloads setup.exe to your
system. Then, run setup and answer all of the questions.
If you have questions or comments, please send them to the Cygwin
mailing list at: cygwin@cygwin.com . I would appreciate it if you would
use this mailing list rather than emailing me directly.
If you want to make a point or ask a question, the Cygwin mailing list
is the appropriate place. This includes ideas and comments about the
setup utility or Cygwin in general.
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:
cygwin-announce-unsubscribe-you=yourdomain.com@cygwin.com
If you need more information on unsubscribing, start reading here:
http://sources.redhat.com/lists.html#unsubscribe-simple
Please read all of the information on unsubscribing that is available
starting at this URL.
reply other threads:[~2004-10-11 0:32 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='002001c4af22$b50e0400$e6ec6f83@robinson.cam.ac.uk' \
--to=maxb@ukf.net \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).