[p4] Codeline comparison question

[Steven Bougon]

Tomasz,

try:
$ p4 help undoc
and look for interchanges:
    p4 interchanges [ -f -l ] -b branch -s fromFile[revRange] [ toFile
... ]

	This command reports which changes have not yet been integrated
	from a set of source files to a set of target files.

	The -f option will show the individual files that would require
	integration. Note that for partially integrated changes, files
may
	be listed even if they have already been integrated
individually.

	The -l flag produces long output with the full text of the
	changelist descriptions.

	A branch view may be given directly on the command line by
stating
	the source (from) and target (to) files, or indirectly by naming
	a stored branch view with -b branch.  A stored branch view may
have
	many mappings, while a view on the command line can only have
one.
	If a stored branch view is given, the target files and source
	files and revisions may be further limited on the command.

	The -r flag reverses the mappings in the branch view, with the
	target files and source files exchanging place.  The -b branch
flag
	is required.

	The -s fromFile[revRange] flag causes the branch view to work
	bidirectionally, where the scope of the command is limited to
	integrations whose 'from' files match fromFile[revRange].  If
	any toFiles are given, the scope is further limited to
integrations
	whose 'to' files match them. When the -s fromFile[revRange] flag
is
	used, -r is ignored, as are any revisions on toFile.  [The -s
flag
	is not meant for end users.  It exists to support graphical
client
	programs.] 

Thanks,
Steven
-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Tomasz Pado
Sent: Thursday, January 18, 2007 1:31 PM
To: perforce-user at perforce.com
Subject: [p4] Codeline comparison question

Hello All,

I have what should be a simple question: how do I compare two codelines
and come up with a list of changelist #s that have gone into one
codeline but did not make it into the other? For example: let's say I
have in the past branched main into 1.0. Over time, there were changes
going into both. All changes that went into 1.0 should have also been
checked into main but not vice versa. How do I make sure that was the
case?

Thanks,
tomasz.
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user