combine(1) [debian man page]

COMBINE(1)																COMBINE(1)

NAME

       combine - combine sets of lines from two files using boolean operations

SYNOPSIS

       combine file1 and file2

       combine file1 not file2

       combine file1 or file2

       combine file1 xor file2

       _ file1 and file2 _

       _ file1 not file2 _

       _ file1 or file2 _

       _ file1 xor file2 _

DESCRIPTION

       combine combines the lines in two files. Depending on the boolean operation specified, the contents will be combined in different ways:

       and Outputs lines that are in file1 if they are also present in file2.

       not Outputs lines that are in file1 but not in file2.

       or  Outputs lines that are in file1 or file2.

       xor Outputs lines that are in either file1 or file2, but not in both files.

       "-" can be specified for either file to read stdin for that file.

       The input files need not be sorted, and the lines are output in the order they occur in file1 (followed by the order they occur in file2
       for the two "or" operations). Bear in mind that this means that the operations are not commutative; "a and b" will not necessarily be the
       same as "b and a". To obtain commutative behavior sort and uniq the result.

       Note that this program can be installed as "_" to allow for the syntactic sugar shown in the latter half of the synopsis (similar to the
       test/[ command). It is not currently installed as "_" by default, but you can alias it to that if you like.

SEE ALSO

       join(1)

AUTHOR

       Copyright 2006 by Joey Hess <joey@kitenet.net>

       Licensed under the GNU GPL.

moreutils							    2012-04-09								COMBINE(1)

merge(1)						      General Commands Manual							  merge(1)

NAME

       merge - three-way file merge

SYNOPSIS

       file1 file2 file3

DESCRIPTION

       combines  two  files  that are revisions of a single original file.  The original file is file2, and the revised files are file1 and file3.
       identifies all changes that lead from file2 to file3 and from file2 to file1, then deposits the merged text into file1.	If the	option	is
       used, the result goes to standard output instead of file1.

       An  overlap  occurs  if both file1 and file3 have changes in the same place.  prints how many overlaps occurred, and includes both alterna-
       tives in the result.  The alternatives are delimited as follows:

	      lines in file1
	      lines in file3

       If there are overlaps, edit the result in file1 and delete one of the alternatives.

       This command is particularly useful for revision control, especially if file1 and file3 are the ends of two branches that have file2  as  a
       common ancestor.

EXAMPLES

       A typical use for is as follows:

	      1.   To  merge  an  RCS branch into the trunk, first check out the three different versions from RCS (see co(1)) and rename them for
		   their revision numbers: 5.2, 5.11, and 5.2.3.3.  File 5.2.3.3 is the end of an RCS branch that split off the trunk at file 5.2.

	      2.   For this example, assume file 5.11 is the latest version on the trunk, and is also a revision  of  the  "original"  file,  5.2.
		   Merge the branch into the trunk with the command:

	      3.   File  5.11  now  contains  all  changes  made on the branch and the trunk, and has markings in the file to show all overlapping
		   changes.

	      4.   Edit file 5.11 to correct the overlaps, then use the command to check the file back in (see ci(1)).

WARNINGS

       uses the ed(1) system editor.  Therefore, the file size limits of ed(1) apply to

AUTHOR

       was developed by Walter F. Tichy.

SEE ALSO

       diff3(1), diff(1), rcsmerge(1), co(1).

																	  merge(1)