[p4] Sync question

Jeff A. Bowles jab at pobox.com
Thu Aug 20 11:39:24 PDT 2009


Also, I would seriously ask about the deletion-in-6.4.7. Is that really the
way you want to "sunset" a development line, given that it absolutely
precludes patch development in that line at any time, ever? (And an
erroneous back-integration from that-line to your main will machine-gun all
the files in your main, popping them off like pepsi cans at your uncle's
shooting fence on the farm.)
I am not saying it is wrong - there are
defensible and good reasons for doing it. I do believe that a
seriously-long discussion with all-the-players on the topic, would be
worth the time. (It is a particular decision that needs to be made
deliberately. I would use permissions, turning off ability to be used
as a source for branches, or turning off write, or turning off all
permissions, to manage an sunset-ed line. Usually.)

   -Jeff Bowles


On Thu, Aug 20, 2009 at 11:33 AM, Jeff A. Bowles <jab at pobox.com> wrote:

> There is a missing piece of information in that scenario.  I think it is
> the text of the delete-message, and would bet a donut (doughnut, to a
> purist) that the 6.4.7 files were going away, but it happened so fast (and
> the adds in 6.4.8 started appearing on the screen just as quickly) that it
> was hard to tell exactly what was going away.
> This is such a standard situation and scenario, that it would have been
> encountered and identified a decade ago, if it were a bug. It's not a bug.
>
> I'd get the exact-commands-typed (or the exact-commands-in-P4V-log) and the
> exact-output together, and compare.  There's a single piece of information
> missing, and I'm willing to bet that you'll find it in the pathnames of the
> commands-given and the output.)
>
> ---
> Jeff Bowles - jeff at vizim.com
>
>
> On Wed, Aug 19, 2009 at 11:27 AM, Jim Walnum <JWalnum at axarosenberg.com>wrote:
>
>> Thanks so much for the quick reply Matt. It seems that 140752 is all
>> file deletes in a dir //depot/dir1/6.4.7/ . 140650 is all adds to
>> another dir //depot/dir1/6.4.8
>>
>>
>>
>> The user says that a force sync works and removes the files deleted in
>> the 140752 change list. He thinks this is a bug.
>>
>>
>>
>> ________________________________
>>
>> From: Matt Janulewicz [mailto:matt.janulewicz at lucasfilm.com]
>> Sent: Wednesday, August 19, 2009 11:18 AM
>> To: Jim Walnum
>> Cc: perforce-user at perforce.com
>> Subject: Re: [p4] Sync question
>>
>>
>>
>> At initial guess is that changelist 140752 contains files that are
>> outside the scope of the workspace (outside //depot/dir1/...)
>>
>> A always think of @changelist notation as being the same as a date, or
>> point in time. So syncing to that changelist will give you files that
>> existed in //depot/dir1/... at the time @140752 existed. If the
>> workspace can't view those files then they won't be synced.
>>
>> It would be interesting to check the output of 'p4 describe 140752' and
>> compare the paths of all the files checked in. I bet they're all outside
>> //depot/dir1/...  All the other changelists between 140650 and 140752
>> are probably the same.
>>
>>
>> -Matt
>>
>>
>> Jim Walnum wrote:
>>
>> I'm a relative noob with Perforce, and I have recently inherited the job
>> as admin. A user has asked me about an apparent problem they are having
>> with a sync to a changelist ID. They run:
>>
>> C:\>p4 -s -u user1 -p perforce:1666 -c shadow_local_machine1 sync
>> //depot/dir1/... at 140752
>>
>> And get:
>>
>> error: //depot/dir1/... at 140752 - file(s) up-to-date.
>> exit: 0
>>
>> But when they run a change report they see the client only has change
>> 140650 (earlier than the 140752 change)
>>
>> C:\>p4 changes -m 1 -t -l //depot/dir1/...@/... at shadow_local_machine1
>>
>> Change 140650 on 2009/08/04 17:06:10 by user1 at shadow_local_machine2
>>
>> Am I missing something obvious?
>>
>> Thanks,
>>
>> - Jim W
>>
>>
>>
>> -----Original Message-----
>> From: perforce-user-bounces at perforce.com
>> [mailto:perforce-user-bounces at perforce.com] On Behalf Of
>> perforce-user-request at perforce.com
>> Sent: Tuesday, August 11, 2009 12:00 PM
>> To: perforce-user at perforce.com
>> Subject: perforce-user Digest, Vol 56, Issue 10
>>
>> Send perforce-user mailing list submissions to
>>        perforce-user at perforce.com
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>        http://maillist.perforce.com/mailman/listinfo/perforce-user
>> or, via email, send a message with subject or body 'help' to
>>        perforce-user-request at perforce.com
>>
>> You can reach the person managing the list at
>>        perforce-user-owner at perforce.com
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of perforce-user digest..."
>>
>>
>> Today's Topics:
>>
>>   1. Re: print? (Charles Summey)
>>   2. Propagating changes from branch to branch (Jason Perry)
>>   3. Copying files and metadata from one server to another
>>      (Pankaj Goyal)
>>   4. Re: Integration preview (Stephen Vance)
>>   5. Re: Copying files and metadata from one server to another
>>      (Stephen Vance)
>>   6. Re: Copying files and metadata from one server to another
>>      (Tim McDaniel)
>>   7. Re: Propagating changes from branch to branch (Rick Macdonald)
>>   8. Hugo Lamelas/CEG/CSC is out of the office. (Hugo Lamelas)
>>   9. Re: Modifying Changelist form (Ivey, William)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 10 Aug 2009 15:31:51 -0400
>> From: Charles Summey <charles.summey at vgt.net>
>> <mailto:charles.summey at vgt.net>
>> To: "perforce-user at perforce.com" <mailto:perforce-user at perforce.com>
>> <perforce-user at perforce.com> <mailto:perforce-user at perforce.com>
>> Subject: Re: [p4] print?
>> Message-ID: <0250C230D4293940865ECA23E708A7871102F8AB94 at ExMB.vgt.net>
>> <mailto:0250C230D4293940865ECA23E708A7871102F8AB94 at ExMB.vgt.net>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> let me slightly update my request.
>>
>> I still use P4Win,
>> when P4Win in opened, in the "Client View of Depot" pane, I might have
>> any number of folders open exposing files,
>> I tried to right click in the pane hoping to select "print"
>> in order to get a hardcopy of the folder contents as shown in the pane,
>>
>> I have also tried to look in the drop down menus for a print option,
>> don't see one;
>> interestingly, I do see the "more" button which does allow me to do page
>> setup for printing; curious!
>> Charles
>>
>>
>>
>> -----Original Message-----
>> From: perforce-user-bounces at perforce.com
>> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Charles Summey
>> Sent: Monday, August 10, 2009 2:16 PM
>> To: perforce-user at perforce.com
>> Subject: [p4] print?
>>
>> I'd like to be able to print to a hardcopy the currently displayed
>> "Client View of Depot"; how do I do that?
>>
>> Charles
>> charles.summey at vgt.net
>> (voice) 434-992-5465
>> (cell) 865-300-4210
>>
>> _______________________________________________
>> perforce-user mailing list  -  perforce-user at perforce.com
>> http://maillist.perforce.com/mailman/listinfo/perforce-user
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Mon, 10 Aug 2009 20:35:07 -0400
>> From: Jason Perry <jperry at choicestream.com>
>> <mailto:jperry at choicestream.com>
>> To: <perforce-user at perforce.com> <mailto:perforce-user at perforce.com>
>> Subject: [p4] Propagating changes from branch to branch
>> Message-ID: <C6A634FB.2AE44%jperry at choicestream.com<C6A634FB.2AE44%25jperry at choicestream.com>
>> >
>> <mailto:C6A634FB.2AE44%25jperry at choicestream.com<C6A634FB.2AE44%2525jperry at choicestream.com>
>> >
>> Content-Type: text/plain;      charset="US-ASCII"
>>
>> Hi,
>>
>> I wanted to find out what you guys think is the best approach for this
>> scenario.
>>
>> Mainline
>> Mainline -> Current Branch off of mainline
>> Mainline -> New Branch off of mainline after Current Branch
>>
>> The ultimate end goal is to get a change made in the Current Branch to
>> Mainline and the New Branch
>>
>> Approach 1
>> 1. A required change is made on the Current Branch
>> 2. The change is then integrated to Mainline from the Current Branch
>> 3. The change is then integrated to the New Branch from the Current
>> Branch
>>
>> Approach 2
>> 1. A required change is made on the Current Branch
>> 2. The change is then integrated to Mainline from the Current Branch
>> 3. The change is then integrated to the New Branch from Mainline
>>
>> Is any of these approaches better than the other?  I am leaning more
>> towards
>> Approach 2 because the integrations will be less conflicting.  With
>> approach
>> 1 though you only have to do one submission.
>>
>> Let me know what you guys think.
>>
>> Thanks,
>> Jay
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Tue, 11 Aug 2009 10:29:47 +0530
>> From: Pankaj Goyal <pankajg at adobe.com> <mailto:pankajg at adobe.com>
>> To: "perforce-user at perforce.com" <mailto:perforce-user at perforce.com>
>> <perforce-user at perforce.com> <mailto:perforce-user at perforce.com>
>> Subject: [p4] Copying files and metadata from one server to another
>> Message-ID:
>>
>> <720662DBBC1A4D4C900396A2E12258AADD9F60E6C9 at INDIAMBX01.corp.adobe.com>
>> <mailto:720662DBBC1A4D4C900396A2E12258AADD9F60E6C9 at INDIAMBX01.corp.adobe
>> .com>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Hi,
>>   I have some directories and files in perforce server say "ABC". Now I
>> want to copy all the directories and files from perforce server "ABC" to
>> another perforce server "XYZ". During this process I also want to copy
>> the metadata of the files, specially the version history and all.
>>
>> Is there any command available on perforce to do this intelligent copy
>> of files ? Any method/script to do similar task will be highly
>> appreciated.
>>
>>
>> Thanks and Regards
>> Pankaj
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Tue, 11 Aug 2009 15:16:40 +1000
>> From: Stephen Vance <steve at vance.com> <mailto:steve at vance.com>
>> To: "Rainey, Mark (Cleveland)" <Mark_Rainey at intuit.com>
>> <mailto:Mark_Rainey at intuit.com>
>> Cc: perforce-user at perforce.com
>> Subject: Re: [p4] Integration preview
>> Message-ID: <4A80FEB8.4030102 at vance.com>
>> <mailto:4A80FEB8.4030102 at vance.com>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> Mark --
>>
>> You may want to e-mail support to add your voice to the request for
>> resolvable deletes. The problem you're having is that there is no way to
>>
>> accept your/theirs for adds or deletes. The Perforce recommendation is
>> to modify the branch spec to include/exclude these things, but there are
>>
>> many of us who feel that's a bit of an inconvenient hack that doesn't
>> scale to large development organizations with developers of varying
>> skill levels.
>>
>> Steve
>>
>> Rainey, Mark (Cleveland) wrote:
>>
>>
>>        I am running the preview for integrations to figure out who
>> hasn't
>>        integrated their work from one branch to another.  There are
>> cases
>>
>>
>> where
>>
>>
>>        an integrate should not happen but I still want the changes off
>> of the
>>        preview.  For example I am previewing the integration from
>> //branch1
>>
>>
>> to
>>
>>
>>        //branch2.  I delete 3 files on //branch1 but those 3 files
>> should
>>
>>
>> exist
>>
>>
>>        on //branch2.  When I run the preview they show up as needing to
>> be
>>        integrated.  Usually if the file exist on both branches I
>> resolve and
>>        say accept yours/target which effectively ignores the merge but
>>
>>
>> creates
>>
>>
>>        the merge record.  But when files are added or deleted you can't
>>        resolve.  So how do I get them off of the preview?
>>
>>
>>
>>        My only thought would be to go ahead with the add or delete on
>>
>>
>> //branch2
>>
>>
>>        and then go on branch2 and back out/rollback that change.  Just
>>        wondering if there is a better solution (and doesn't include
>> putting
>>        specific files in the branch spec).
>>
>>
>>
>>        Thank you,
>>
>>
>>
>>        Mark Rainey
>>
>>        Sr. Software Configuration Engineer
>>
>>
>>
>>        Intuit Real Estate Solutions
>>
>>        216.825.6641
>>
>>        mark_rainey at intuit.com <mailto:mark_rainey at intuit.com>
>> <mailto:mark_rainey at intuit.com>
>>
>>        www.realestate.intuit.com <http://www.realestate.intuit.com>
>> <http://www.realestate.intuit.com>
>>
>>
>>
>>        Please consider the environment before printing this email.
>>
>>        _______________________________________________
>>        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
>>
>
>



More information about the perforce-user mailing list