From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Tim Waugh <twaugh@redhat.com>
Cc: patchutils-list@sourceware.org
Subject: Re: How to resolve hiccups by patch program?
Date: Fri, 05 Jan 2007 21:51:00 -0000 [thread overview]
Message-ID: <459EC80F.6020409@users.sourceforge.net> (raw)
In-Reply-To: <1167996075.8061.3.camel@cyberelk.elk>
> In any case, patchutils is not involved.
>
Well, you are right. - But I hope that your tool box can help to extract
code places that might be problematic.
Application of your tools:
1. I want to look at a specific patch that is a part of a bigger file.
$ filterdiff -i 'app_adsiprog.c' < const4.patch
2. I have tried an example that is provided in your manual.
http://man-wiki.net/index.php/1:filterdiff
$ filterdiff -i '*.c' --lines=-5 < const4.patch
I don't get any output from those commands. Do I make a mistake here?
Regards,
Markus
next prev parent reply other threads:[~2007-01-05 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 10:26 SF Markus Elfring
2007-01-05 11:21 ` Tim Waugh
2007-01-05 21:51 ` SF Markus Elfring [this message]
2007-01-06 15:03 ` SF Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2007-01-05 12:08 SF Markus Elfring
2007-01-04 8:04 SF Markus Elfring
2007-01-04 14:04 ` Tim Waugh
2007-01-04 22:04 ` SF Markus Elfring
2007-01-03 10:47 SF Markus Elfring
2007-01-03 12:43 ` Tim Waugh
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=459EC80F.6020409@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=patchutils-list@sourceware.org \
--cc=twaugh@redhat.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).