[p4] Feature request: P4 job as revision range specifier

Jeff A. Bowles jab at pobox.com
Tue Mar 25 15:39:54 PDT 2008

I assume you sent this to Perforce Technical Support; they're the ones you
ask for these sorta things.
Be prepared, when you ask for this, to answer this question: "but what about
the job that corresponds to five changelists, and has multiple revisions of
a specific single file referenced by that job?"  (This is the situation,
"oops!  I needed to fix-the-fix before handing to QA. Now, where was the bug
number it fixed...")

What should it do in the workspace for the files that weren't included
/addressed by that job? Remove them? Leave them alone? (If you're aiming for
a job in a revision range, the semantics of files/revision-ranges lead to
that as the second question.)

Don't get me wrong - I think it's a good idea. But to make it feel
"consistent" with existing syntax / semantics takes a bit of time with
questions like this.

  -Jeff Bowles

On Tue, Mar 25, 2008 at 2:22 PM, Calman, Kevin <Kevin.Calman at acs-inc.com>

>    If this hasn't been request in the past, I would like to request the
> following feature from Perforce: allow use of a job in a revision range.
>    We use the P4DTI to synchronize P4 jobs to Bugzilla bugs, and then use
> those bugs as atomic units of work to drop code in to builds. It would be
> really useful to be able to sync a workspace to all the changelists in a
> particular bug (job) in a single operation.
>    Currently, we use a wrapper script to build a private label from the
> changelists in a job, and then sync that, but it is a drag.
> --
> Opinions herein are exclusively my own, unless you share them.
> Kevin Calman, kevin.calman at acs-inc.com, +1-512-671-2647
> "CONFIDENTIALITY NOTICE: This email message, including any attachments, is
> for the sole use of the intended recipient(s) and may contain confidential
> and privileged information. Any unauthorized review, use, disclosure, or
> distribution is prohibited. If you are not the intended recipient, please
> contact the sender by reply email and destroy all copies of the original
> message."
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

Jeff Bowles - jeff.a.bowles at gmail.com

More information about the perforce-user mailing list