Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
UNICEF

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 128 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

filterdiff



SYNOPSIS

       filterdiff [-i PATTERN] [-p n] [--strip=n]
                  [--addprefix=PREFIX] [-x PATTERN] [--verbose]
                  [-v] [-z] [-# RANGE | --hunks=RANGE]
                  [--lines=RANGE] [--annotate] [--format=FORMAT]
                  [--as-numbered-lines=WHEN] [file...]

       filterdiff {--help | --version | --list | --grep ...}


DESCRIPTION

       You  can  use filterdiff to obtain a patch that applies to
       files matching the shell wildcard PATTERN  from  a  larger
       collection  of patches. For example, to see the patches in
       patch-2.4.3.gz that apply to all files called lp.c:

              filterdiff -z -i '*/lp.c' patch-2.4.3.gz

       If neither -i nor -x options are given, -i '*' is assumed.
       To  remove lines from a file that are not part of a patch,
       you might do this:

              filterdiff message > patch

       Note that the interpretation of the shell wildcard pattern
       does  not count slash characters or periods as special (in
       other words, no flags are given to fnmatch).  This  is  so
       that  ``*/basename''-type  patterns  can  be given without
       limiting the number of pathname components.

       You can use both unified and  context  format  diffs  with
       this program.


OPTIONS

       -i PATTERN
              Include  only  files  matching  PATTERN.  All other
              lines in the input are suppressed.

       -x PATTERN
              Exclude files matching PATTERN. All other lines  in
              the input are displayed.

              original file that lie within the specified  RANGE.
              Lines  are numbered from 1, and the range is a com­
              ma-separated  list  of  numbers  or  ``first-last''
              spans; either the first or the last in the span may
              be omitted to indicate no limit in that  direction.

       --annotate
              Annotate  each hunk with the filename and hunk num­
              ber.

       --format=unified|context
              Use specified output format.

       --strip=n
              Remove the first n components of pathnames  in  the
              output.

       --addprefix=PREFIX
              Prefix pathnames in the output by PREFIX.

       --as-numbered-lines=before|after
              Instead  of  a patch fragment, display the lines of
              the selected hunks with the line number of the file
              before (or after) the patch is applied, followed by
              a TAB character and a colon, at  the  beginning  of
              each  line.  Each hunk except the first will have a
              line consisting of ``...'' before it.

       -v, --verbose
              Always show non-diff lines in the  output.  By  de­
              fault, non-diff lines are only shown when excluding
              a filename pattern.

       -z     Decompress files with extensions .gz and .bz2.

       --help Display a short usage message.

       --version
              Display the version number of filterdiff.

       --list Behave like lsdiff(1) instead.


              filterdiff -#1 patchfile

       To see patches modifying a ChangeLog file in a subdirecto­
       ry, use:

              filterdiff -p1 Changelog

       To see the complete patches for each patch  that  modifies
       line 1 of the original file, use:

              filterdiff --lines=1 patchfile | lsdiff | \
                xargs -rn1 filterdiff patchfile -i

       To  see  all but the first hunk of a particular patch, you
       might use:

              filterdiff -p1 -i file.c -#2- foo-patch

       If you have a very specific list of hunks in a patch  that
       you want to see, list them:

              filterdiff -#1,2,5-8,10,12,27-

       To  see  the  lines  of the files that would be patched as
       they will appear after the patch is applied, use:

              filterdiff --as-numbered-lines=after patch.file

       You can see the same context before the patch  is  applied
       with:

              filterdiff --as-numbered-lines=before


AUTHOR

       Tim Waugh <twaugh@redhat.com>.

patchutils                 23 Aug 2002              FILTERDIFF(1)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =


  

More information about the site can be found in the FAQ


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.08 Seconds