Greetings All!!
I have a very peculiar problem where I have to parse a big text file and extract useful data out of it with starting and ending block pattern matching.
e.g. I have a input file like this:
sample data
block1
sample data
start
useful data
end
sample data
block2
sample... (5 Replies)
Hi,
I have file (FILE.tmp) having contents,
FILE.tmp
========
filename=menudata
records=0000000000037
ldbname=pinsys
timestamp=2005/05/14-18:32:33
I want to parse it bring a new file which will look like,
filename records ldbname timestamp... (2 Replies)
I have a file that is large and is broken up by groups of data. I want to take certain fields and display them different to make it easier to read. Given input file below:
2008 fl01 LAC 2589 polk doal
xx 2008q1 mx
sect 25698541
Sales 08 Dept group
lead1 ... (8 Replies)
Hi all,
I wud like to get ur assistance in retrieving lines containing l1.My excel dataset contains around 8000 lines.I converted it into a text tab delimiter file and got the lines containing l1,My output is a list of lines containing l1 saved in a outfile.Some of d lines from my outfile s... (5 Replies)
Hi,
I have a folder that contains many (multiple) files
1.fasta
2.fasta
3.fasta
4.fasta
5.fasta
.
.
100's of files
Each such file have data in the following format
for example:
vi 1.fasta
>AB_1 gi|15835212|ref|NP_296971.1| preprotein translocase subunit SecE... (3 Replies)
Hi All,
I need some help to effectively parse out a subset of results from a big results file.
Below is an example of the text file. Each block that I need to parse starts with "Output of GENE for sequence file 100.fasta" (next block starts with another number). I have given the portion of... (8 Replies)
I have 2 text files where I need to parse data from file 2 using the data from file 1. Below are my sample files
File 1 (tab delimited)
257 350
670 845
725 1025
767 820
...
....
....
file 2 (tab delimited)
220..450 TA AB650 ABCED
520..850 GA AB720 ABCDE
700..1100 TC AB820 ABCDE... (2 Replies)
Im really beginner in this case, maybe someone can help me find the answer:
if my input file like this:
void main(int a, int b){
int x; double y;
printf("file");
}
and i want output like this:
int a
int b
int x
double y
A awk script that can parse only data tipe, im confused.
what... (2 Replies)
Hey Guys,
I'm a novice at shell scripts and i need some help parsing file data.
Basically, I want to write a script that retrieves URLs.
Here is what I have so far.
#!/bin/bash
echo "Please enter start date (format: yyyy-mm-dd):\c"
read STARTDATE
echo "Please enter end date... (7 Replies)
Discussion started by: silverdust
7 Replies
LEARN ABOUT SUSE
git-update-ref
GIT-UPDATE-REF(1) Git Manual GIT-UPDATE-REF(1)NAME
git-update-ref - Update the object name stored in a ref safely
SYNOPSIS
git update-ref [-m <reason>] (-d <ref> [<oldvalue>] | [--no-deref] <ref> <newvalue> [<oldvalue>])
DESCRIPTION
Given two arguments, stores the <newvalue> in the <ref>, possibly dereferencing the symbolic refs. E.g. git update-ref HEAD <newvalue>
updates the current branch head to the new object.
Given three arguments, stores the <newvalue> in the <ref>, possibly dereferencing the symbolic refs, after verifying that the current value
of the <ref> matches <oldvalue>. E.g. git update-ref refs/heads/master <newvalue> <oldvalue> updates the master branch head to <newvalue>
only if its current value is <oldvalue>. You can specify 40 "0" or an empty string as <oldvalue> to make sure that the ref you are creating
does not exist.
It also allows a "ref" file to be a symbolic pointer to another ref file by starting with the four-byte header sequence of "ref:".
More importantly, it allows the update of a ref file to follow these symbolic pointers, whether they are symlinks or these "regular file
symbolic refs". It follows real symlinks only if they start with "refs/": otherwise it will just try to read them and update them as a
regular file (i.e. it will allow the filesystem to follow them, but will overwrite such a symlink to somewhere else with a regular
filename).
If --no-deref is given, <ref> itself is overwritten, rather than the result of following the symbolic pointers.
In general, using
git update-ref HEAD "$head"
should be a lot safer than doing
echo "$head" > "$GIT_DIR/HEAD"
both from a symlink following standpoint and an error checking standpoint. The "refs/" rule for symlinks means that symlinks that point to
"outside" the tree are safe: they'll be followed for reading but not for writing (so we'll never write through a ref symlink to some other
tree, if you have copied a whole archive by creating a symlink tree).
With -d flag, it deletes the named <ref> after verifying it still contains <oldvalue>.
LOGGING UPDATES
If config parameter "core.logAllRefUpdates" is true or the file "$GIT_DIR/logs/<ref>" exists then git update-ref will append a line to the
log file "$GIT_DIR/logs/<ref>" (dereferencing all symbolic refs before creating the log name) describing the change in ref value. Log lines
are formatted as:
1. oldsha1 SP newsha1 SP committer LF
Where "oldsha1" is the 40 character hexadecimal value previously stored in <ref>, "newsha1" is the 40 character hexadecimal value of
<newvalue> and "committer" is the committer's name, email address and date in the standard GIT committer ident format.
Optionally with -m:
1. oldsha1 SP newsha1 SP committer TAB message LF
Where all fields are as described above and "message" is the value supplied to the -m option.
An update will fail (without changing <ref>) if the current user is unable to create a new log file, append to the existing log file or
does not have committer information available.
AUTHOR
Written by Linus Torvalds <torvalds@osdl.org[1]>.
GIT
Part of the git(1) suite
NOTES
1. torvalds@osdl.org
mailto:torvalds@osdl.org
Git 1.7.1 07/05/2010 GIT-UPDATE-REF(1)