From: Mark Phillips <M.S.Phillips@nortel.co.uk>
To: "Joseph H. Buehler" <jhpb@sarto.gaithersburg.md.us>
Cc: egcs@cygnus.com
Subject: Re: no patch to .brik in latest snapshot diff!
Date: Tue, 20 Jan 1998 04:46:00 -0000 [thread overview]
Message-ID: <Pine.HPP.3.95q.980120095937.463F-100000@bharh59a.europe.nortel.com> (raw)
In-Reply-To: <m2soqmkkhv.fsf@altera.gaithersburg.md.us>
If you upgrade to GNU patch 2.5, it supports doing this for you (see -Z
and -T options). You do need to be careful when creating the patches
though (see the man page).
The later version of patch also deals better with creating files from
scratch and removing files.
Have fun
Mark
PS. Note the default behaviour of patch has changed - you may want -bv
Mark S. Phillips ESN 742 2461
msp@nortel.co.uk Tel. +44 1279 402461
On 18 Jan 1998, Joseph H. Buehler wrote:
> Joe Buck <jbuck@synopsys.com> writes:
>
> > We've persistently had problems with diffs. It seems that there should
> > be a better way to safely automate the process, e.g. a script that takes
> > two xxx.tar.gz files and produces a diff that is guaranteed to turn the
> > first one into the second one. If this were done once it would never
> > go wrong again.
>
> I would like to see something to get the file dates correct after
> "patch" is done, also.
>
> Joe Buehler
>
next prev parent reply other threads:[~1998-01-20 4:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <January_18_1998_at_05_18_16_7755_Joseph_H._Buehler@altera>
1998-01-19 2:30 ` Joseph H. Buehler
1998-01-20 4:46 ` Mark Phillips [this message]
1998-01-16 20:09 Joe Buck
1998-01-17 22:09 ` Jeffrey A Law
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=Pine.HPP.3.95q.980120095937.463F-100000@bharh59a.europe.nortel.com \
--to=m.s.phillips@nortel.co.uk \
--cc=egcs@cygnus.com \
--cc=jhpb@sarto.gaithersburg.md.us \
/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).