[p4] Editing a Branch spec

[Jeff A. Bowles]

It is worth remembering that a "named branch spec" is, really,
a convenient abbreviation for remembering "A -> B" so
you do not have to retype (mistype) the pathnames when you
run "p4 integrate A/...  B/..."

The command "p4 integrate -b specname" and the
above "p4 integrate A/... B/..." do the same thing.

There are small details that might make it seem like it is
a bigger thing, but it's really just an abbreviation / shorthand
stored in the server tables.  (The two quick examples are
that you can specific "src1 -> target1 and src2->target2"
and you can say "don't copy src1/version.h at all".)

If you run "p4 integ -b specname ; p4 submit" and then
delete the spec, you've just deleted an abbrevation. The
target still exists.

The closest analogy is moving to a new house, and
then tearing up the map you showed to the movers after
you moved in. The house you now live in didn't get razed
because you destroyed the map; the map can be redrawn
with the same "from" and "to" and used to have additional
stuff moved (the things from E-Bay that arrived yesterday
to the old address).

And if someone puts something in the "source" that you
don't wanna propagate later, that's the equivalent of
scratching it off the map ("putting an 'X' on a room to
indicate not to move the spiders in that room to the
new place.")

Hope the metaphor's not too silly...

  -Jeff Bowles
   Perforce Consulting Partner

On 5/10/07, Melissa Kacher <mkacher at msn.com> wrote:
> You'll need to delete the files from your branch by hand. Branch specs are
> not retroactive. And they only affect files that are actually in the spec.
> Since the files in question are no longer in the spec, they will never be
> touched again when you integrate using that branch spec.
>
>
> ----Original Message Follows----
> From: "R K" <r.keralaiyer at gmail.com>
> To: perforce-user at perforce.com
> Subject: [p4] Editing a Branch spec
> Date: Thu, 10 May 2007 09:56:33 +0530
> MIME-Version: 1.0
> Received: from frankenrouter.perforce.com ([67.101.114.82]) by
> bay0-mc11-f13.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Wed, 9
> May 2007 21:40:26 -0700
> Received: from p4tress.perforce.com (localhost [127.0.0.1])by
> frankenrouter.perforce.com (8.13.0.PreAlpha5/8.13.0.PreAlpha5) with ESMTP id
> l4A4QdR5050250;Wed, 9 May 2007 21:27:00 -0700 (PDT)
> Received: from waypost.perforce.com ([10.199.0.13])by
> frankenrouter.perforce.com (8.13.0.PreAlpha5/8.13.0.PreAlpha5) withESMTP id
> l4A4Qbdf050246for <perforce-user at perforce.com>; Wed, 9 May 2007 21:26:37
> -0700 (PDT)
> Received: from an-out-0708.google.com ([209.85.132.241])by
> waypost.perforce.com with ESMTP; 09 May 2007 21:26:37 -0700
> Received: by an-out-0708.google.com with SMTP id c16so98276anafor
> <perforce-user at perforce.com>; Wed, 09 May 2007 21:26:34 -0700 (PDT)
> Received: by 10.100.211.11 with SMTP id j11mr964413ang.1178771193880;Wed, 09
> May 2007 21:26:33 -0700 (PDT)
> Received: by 10.100.167.19 with HTTP; Wed, 9 May 2007 21:26:33 -0700 (PDT)
> X-Message-Info:
> LsUYwwHHNt1Z3XYBI0K3H6vNEz2mZE0hc6JZuGJZ15O/TKANVc32eHBjl6f+nuHy
> X-IronPort-Anti-Spam-Filtered: true
> X-IronPort-Anti-Spam-Result: Ao8CAGM7QkbRVYTxhmdsb2JhbACCQTiNAQIBCAgECQcb
> X-IronPort-AV: i="4.14,515,1170662400"; d="scan'208";
> a="1206444:sNHT43423550"
> DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com;
> s=beta;h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;b=H3RnZ2pt8Jh5zCe2GbD8ZUAoMs30VuIegu4GMfJOGjC52VvMRR4pCb8AUEW4xo2RpIMw///CU1uDqh5dT2+1yZx08MByVpF4UdGMJDaaf15NY6cLS9gvI6p4JtT05gEaHU77JuRcfUaV3vBWfjxAswx9TYcem1y1C/VoBDQcif8=
> DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com;
> s=beta;h=received:message-id:date:from:to:subject:mime-version:content-type;b=CJLxo92uvrdm+5Ik0pEuxHmYUFN8Ov5qBcgyXDk+7LeQZEXMsPuXtpUQvUclqQI2FuR5VNE6D8fbmMq5BGHMi3zewRuO9zdXDXoxIUnhrR+R5jqaqyOQUmz/Fo+qYfJYxPj/X4si/fb7haWVtLx+/JbBxZnCVAOCJ3Z2P/UUs8o=
> X-Content-Filtered-By: Mailman/MimeDel 2.1.6
> X-BeenThere: perforce-user at perforce.com
> X-Mailman-Version: 2.1.6
> Precedence: list
> List-Id: Discuss Perforce with other users <perforce-user.perforce.com>
> List-Unsubscribe:
> <http://maillist.perforce.com/mailman/listinfo/perforce-user>,
> <mailto:perforce-user-request at perforce.com?subject=unsubscribe>
> List-Archive: <http://maillist.perforce.com/pipermail/perforce-user>
> List-Post: <mailto:perforce-user at perforce.com>
> List-Help: <mailto:perforce-user-request at perforce.com?subject=help>
> List-Subscribe:
> <http://maillist.perforce.com/mailman/listinfo/perforce-user>,
> <mailto:perforce-user-request at perforce.com?subject=subscribe>
> Errors-To: perforce-user-bounces at perforce.com
> Return-Path: perforce-user-bounces at perforce.com
> X-OriginalArrivalTime: 10 May 2007 04:40:26.0920 (UTC)
> FILETIME=[5499FA80:01C792BD]
>
> All,
>
> I have a branch spec wherein i get files from different folders of one
> branch (Integration already done ) .I  now want to edit my branch spec such
> that i remove source paths for 2 folders ( I do not need them to be in my
> branch ) . If i integrate once again will the files under those 2 folders in
> my branch  be deleted or will they continue to exist ?
>
> Regards
> Ram
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>


-- 
---
Jeff Bowles - jab at piccoloeng.com