I have a folder called {homedata}
Within this folder there are 12 subfolders 200601.......200612
Within each subfolder there are 8 sets of files
Each filename commences with A B C D E F G or H,
so {filename}* can be used.
I am trying to write a script which will from the top level
go... (1 Reply)
Hello
I am currently having problems in mapulating a certain file which contains vaious data.
Belos is a sample content
Event=<3190>
Client IP=<151.111.11.143> DNS=<abc.sbc.com> TransCount=<139>
Client IP=<150.222.133.163> DNS=<xyz.yuu.com> TransCount=<3734>
Event=<3120>
Client... (11 Replies)
Hi everyone..
I am new here, hello.. I hope this doesn't come across to you folks as a stupid question, I'm somewhat new to scripting :)
I'm seeking some help in finding a way to manipulate data output for every two characters - example:
numbers.lst contains the following output:... (3 Replies)
i have a file in follwing format
0110
1020
1011
1032
1020
2005
2003
1050
i want the output in such a way that all non zero numbers will be converted into 1
like this
0110
1010
1011
1011
1010
1001
1001
1010 (3 Replies)
Hi all!
my first post here, so mods -- if this should ideally be in the scripts section, please move there. Thanks!
I have data in the following format:
key1:value1 key2:value2 key3:value3
A
B
C
D
key1:value4 key2:value5 key3:value6
A1
B1
key1: ...
and so on
I want an output... (2 Replies)
Dear all
I have a dataset (in text format,delimited by tab) which have 100 variables (say, var0-var99) and more than 100,000 observations. I want to do the following:
1. for variable var0-var49, I want to add "00" in front of each data (for example, "1" would become "001")
2. for variable... (8 Replies)
Hallo Team,
I need to manipulate existing data file. Have a look at current data and expected data:
Current Data:
27873517141
27873540000
27873515109
27873517140
27873540001
27873540000
27873501343
27873540000
27873517140
27873511292
27873645989
27873540000
27873540000... (7 Replies)
Dear Sir,
I have file input
RGR001|108.28|-2.86489|100-120|RANGGAR
RGR002|108.071|-2.69028|80-100|RANNGAR
RGR003|108.168|-2.97053|50-80|RANNGAR
RGR007|108.192722222|-2.766138889|0-50|RANGGARI want to create files by joining each rows with each rows below
Output as below
... (4 Replies)
Hallo Team,
I need your help. I have a file that has two colums. See sample below:
105550 0.28
105550 0.24
125550 0.28
125550 0.24
215650 0.28
215650 0.24
315550 0.28
315550 0.24
335550 0.28
335550 0.24
40555 0.21
40555 0.17
415550 0.21
415550 0.17
43555 0.21
43555 0.17 (5 Replies)
Discussion started by: kekanap
5 Replies
LEARN ABOUT REDHAT
filterdiff
FILTERDIFF(1)FILTERDIFF(1)NAME
filterdiff - extract or exclude diffs from a diff file
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.
-p n When matching, ignore the first n components of the pathname.
-# RANGE | --hunks=RANGE
Only include hunks within the specified RANGE. Hunks are numbered from 1, and the range is a comma-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.
--lines=RANGE
Only include hunks that contain lines from the original file that lie within the specified RANGE. Lines are numbered from 1, and the
range is a comma-separated list of numbers or ``first-last'' spans; either the first or the last in the span may be omitted to indi-
cate no limit in that direction.
--annotate
Annotate each hunk with the filename and hunk number.
--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 con-
sisting of ``...'' before it.
-v, --verbose
Always show non-diff lines in the output. By default, 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.
--grep Behave like grepdiff(1) instead.
EXAMPLES
To see all patch hunks that affect the first five lines of a C file:
filterdiff -i '*.c' --lines=-5 < patch
To see the first hunk of each file patch, use:
filterdiff -#1 patchfile
To see patches modifying a ChangeLog file in a subdirectory, 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
patch.file
Filterdiff can also be used to convert between unified and context format diffs:
filterdiff -v --format=unified context.diff
SEE ALSO lsdiff(1), grepdiff(1)AUTHOR
Tim Waugh <twaugh@redhat.com>.
patchutils 23 Aug 2002 FILTERDIFF(1)