12-13-2018
Please define what you mean by merge.
Maybe providing a desired output given your sample inputs.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have created these files in a particular directory
a_1.txt
a_2.txt
...
..
a_n.txt
Each file has a single line.
I want to write a output file a.txt, which will have concantated value of string from all the files.
which utility should i use. copy, cat or paste????
Can anyone help... (5 Replies)
Discussion started by: u263066
5 Replies
2. Shell Programming and Scripting
Hello guys,
I gotta question, i have a lot of log files (simple text) and i need to merge them in group of 10 files, one next to the other, that have sense?
For example, i have the files:
File1
File2
File3
File4
.
.
File100
I need to merge the contents of each file into a new file... (3 Replies)
Discussion started by: lestat_ecuador
3 Replies
3. Shell Programming and Scripting
Hi,
i have the files f1 and f2 like:
files f1:
c1 a1
c2 a2
c3 a3
file f2:
c1 b1
c2 b2
c3 b3
i want merge the f1 and f2 file to f3 file like:
c1 a1 b1
c2 a2 b3
c3 a3 b3........
....
.
.
please help me onthis..... (5 Replies)
Discussion started by: koti_rama
5 Replies
4. Shell Programming and Scripting
hi,
i am facing a problem in merging two files using awk,
the problem is as stated below,
file1:
A|B|C|D|E|F|G|H|I|1
M|N|O|P|Q|R|S|T|U|2
AA|BB|CC|DD|EE|FF|GG|HH|II|1
....
....
....
file2 :
1|Mn|op|qr (2 Replies)
Discussion started by: shashi1982
2 Replies
5. Shell Programming and Scripting
hi
i have two files
file1
1234567
1234678
1234679
file2
98765|jjkskk|9393|iyutr
98765|kkooo|9393|hjjjd
98765|abcvfg|9393|sskds
output should be
1234567|jjkskk|9393|iyutr
1234678|kkooo|9393|hjjjd
1234679|abcvfg|9393|sskds (5 Replies)
Discussion started by: mad_man12
5 Replies
6. Shell Programming and Scripting
Given are File A and File B
File A has for example 5 lines:
AAA
BBB
CCC
DDD
EEE
File B has 3 lines:
111
222
333
How can i merge A and B into:
111
222
333
AAA (first line from A)
then a new file: (4 Replies)
Discussion started by: Y-T
4 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I would like to know how can I merge files based on their coordinates, but mantaining the score of each file in the output file like:
Note: 1st column is for chromosome, 2nd for start, 3rd for end of segment, 4th for score
file1:
1 200 300 20
1 400 500 30
file2:
1 200 350 30
1... (1 Reply)
Discussion started by: fadista
1 Replies
8. Shell Programming and Scripting
Hi,
My requirement is,there is a directory location like:
:camp/current/
In this location there can be different flat files that are generated in a single day with same header and the data will be different, differentiated by timestamp, so i need to verify how many files are generated... (10 Replies)
Discussion started by: srikanth_sagi
10 Replies
9. Shell Programming and Scripting
Dear Gents,
Please I need your help... I need small script :) to do the following.
I have a thousand of files in a folder produced daily.
I need first to merge all files called. txt (0009.txt, 0010.txt, 0011.txt) and and to output a resume of all information on 2 separate files in csv... (14 Replies)
Discussion started by: jiam912
14 Replies
10. Programming
Dear Team,
I am using DB2 v10.5 and trying to load huge data using MERGE option ( 10-12 Million) using below query. Basically it loads data from staging to target . Staging table schemaname.Customer_Staging has 12 Million records . Runs for 25 Mins for just select query. But while doing merge... (2 Replies)
Discussion started by: Perlbaby
2 Replies
LEARN ABOUT DEBIAN
git-merge-base
GIT-MERGE-BASE(1) Git Manual GIT-MERGE-BASE(1)
NAME
git-merge-base - Find as good common ancestors as possible for a merge
SYNOPSIS
git merge-base [-a|--all] <commit> <commit>...
git merge-base [-a|--all] --octopus <commit>...
git merge-base --independent <commit>...
DESCRIPTION
git merge-base finds best common ancestor(s) between two commits to use in a three-way merge. One common ancestor is better than another
common ancestor if the latter is an ancestor of the former. A common ancestor that does not have any better common ancestor is a best
common ancestor, i.e. a merge base. Note that there can be more than one merge base for a pair of commits.
OPERATION MODE
As the most common special case, specifying only two commits on the command line means computing the merge base between the given two
commits.
More generally, among the two commits to compute the merge base from, one is specified by the first commit argument on the command line;
the other commit is a (possibly hypothetical) commit that is a merge across all the remaining commits on the command line.
As a consequence, the merge base is not necessarily contained in each of the commit arguments if more than two commits are specified. This
is different from git-show-branch(1) when used with the --merge-base option.
--octopus
Compute the best common ancestors of all supplied commits, in preparation for an n-way merge. This mimics the behavior of git
show-branch --merge-base.
--independent
Instead of printing merge bases, print a minimal subset of the supplied commits with the same ancestors. In other words, among the
commits given, list those which cannot be reached from any other. This mimics the behavior of git show-branch --independent.
OPTIONS
-a, --all
Output all merge bases for the commits, instead of just one.
DISCUSSION
Given two commits A and B, git merge-base A B will output a commit which is reachable from both A and B through the parent relationship.
For example, with this topology:
o---o---o---B
/
---o---1---o---o---o---A
the merge base between A and B is 1.
Given three commits A, B and C, git merge-base A B C will compute the merge base between A and a hypothetical commit M, which is a merge
between B and C. For example, with this topology:
o---o---o---o---C
/
/ o---o---o---B
/ /
---2---1---o---o---o---A
the result of git merge-base A B C is 1. This is because the equivalent topology with a merge commit M between B and C is:
o---o---o---o---o
/
/ o---o---o---o---M
/ /
---2---1---o---o---o---A
and the result of git merge-base A M is 1. Commit 2 is also a common ancestor between A and M, but 1 is a better common ancestor, because 2
is an ancestor of 1. Hence, 2 is not a merge base.
The result of git merge-base --octopus A B C is 2, because 2 is the best common ancestor of all commits.
When the history involves criss-cross merges, there can be more than one best common ancestor for two commits. For example, with this
topology:
---1---o---A
/
X
/
---2---o---o---B
both 1 and 2 are merge-bases of A and B. Neither one is better than the other (both are best merge bases). When the --all option is not
given, it is unspecified which best one is output.
SEE ALSO
git-rev-list(1), git-show-branch(1), git-merge(1)
GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GIT-MERGE-BASE(1)