[p4] How to findout changes in the current client

Thandesh V.K thanvk at gmail.com
Tue Aug 10 07:44:26 PDT 2010


I am afraid to give up :(

Thanks
Thandesh

On Tue, Aug 10, 2010 at 4:51 PM, <buckmeisterq at gmail.com> wrote:

> What I'm hearing is that if you want a way to get all changes from the
> current client only, excluding any old changes submitted by an old client
> with the same name... is that you need to enforce unique client names.
>
> I'd bet even if you scripted something to check client creation and access
> time, creating a new client with the same name as an old one would update
> those timestamps and *still* show you old changes from the old client.
>
>
> Thanks,
> Peter
>
> -----Original Message-----
> From: "Thandesh V.K" <thanvk at gmail.com>
>  Sender: perforce-user-bounces at perforce.com
> Date: Tue, 10 Aug 2010 13:14:09
> To: Sheizaf, Yariv<yariv.sheizaf at sap.com>
> Cc: perforce-user at perforce.com<perforce-user at perforce.com>
> Subject: Re: [p4] How to findout changes in the current client
>
> Thanks for all suggestion/discussion.
> Currently when i do "p4 changes -s submitted -c <client name>", I get even
> old changes as client name is the key - this part is pretty clear.
>
> Let me reword my problem:
> Is there a way to get the list of submitted changes from the *current*
> client with out using client name (any way of using may be pwd or any other
> approach)?
>
> What I am thinking after hearing from all of you is to get all submitted
> changes from that client name and based on
> client creation time (my spec depot is not active), group it to old and
> new.
>
> Thinking how to get client creation time as client spec has
>
> #  Update:      The date this specification was last modified.
> #  Access:      The date this client was last used in any way.
> Thanks
> Thandesh
>
> 2010/8/10 Sheizaf, Yariv <yariv.sheizaf at sap.com>
>
> > Hi,
> >
> > If the spec depot is active, you can find when the client was deleted and
> > when a new client with the same name was created, and filter "p4 changes"
> > command output accordingly.
> >
> > Regards,
> > Yariv Sheizaf
> >
> >
> > Original message:
> > Date: Mon, 9 Aug 2010 18:50:59 +0530
> > From: "Thandesh V.K" <thanvk at gmail.com>
> > To: perforce-user at perforce.com
> > Subject: [p4] How to findout changes in the current client
> > Message-ID:
> >        <AANLkTimmeWLPk-bCwLtWSBdAnLoabCqXKPmOJzKPOa27 at mail.gmail.com>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Hi Folks,
> >
> > I have a client and want to find out all change numbers (either submitted
> > or
> > pending ) from that client.
> > So far, i was using
> >
> > %p4 changes -c <client name>
> >
> > But looks like I am doing wrong. What if there was client with <client
> > name>
> > and there was few submits in that and
> > and that is deleted and recreated a new client with the same name but no
> > changes (submitted or pending) in the new client (but old name).
> >
> > Any solution?
> >
> >
> >
> >
> -------------------------------------------------------------------------------------------------------------
> > " The only thing worst then losing, is quitting."
> >
> > Your Non Quiting Friend
> > Thandesha V.K
> >
> >
> ----------------------------------------------------------------------------------------------------------------------
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Mon, 9 Aug 2010 10:08:42 -0500
> > From: <Kevin_Calman at Dell.com>
> > To: <thanvk at gmail.com>, <perforce-user at perforce.com>
> > Subject: Re: [p4] How to findout changes in the current client
> > Message-ID:
> >        <
> > CC5E27569CC1F343A3E435A5ED53525B9B068BE158 at AUSX7MCPC101.AMER.DELL.COM>
> >
> > Content-Type: text/plain; charset="us-ascii"
> >
> > Thandesh,
> >        Are you saying that you are, or are not, seeing old (pre-deletion)
> > changes reported against a recreated client spec name? I would expect
> that
> > to be the case. A client's name is its unique key; if it is deleted and
> new
> > client created it with the same name, I would expect that to be treated
> as
> > the same client. You could check this by examining the revision history
> of
> > the client spec file in a 'spec depot'.
> >        Assuming this is the case, why would you want to reset the change
> > history of a client by deleting and recreating it? Are you trying to use
> > client spec name as a key into per-issue branching? If the history is
> that
> > relevant, then just create new, uniquely named client specs.
> >        If this were not the case, how would you access the change history
> > by client spec name from before the most recent deletion?
> > --
> > Kevin Calman,  Software Build & Release Engineer
> > Dell Modular Services Product Group, Austin TX US
> >
> >
> > -----Original Message-----
> > From: perforce-user-bounces at perforce.com [mailto:
> > perforce-user-bounces at perforce.com] On Behalf Of Thandesh V.K
> > Sent: Monday, August 09, 2010 8:21 AM
> > To: perforce-user at perforce.com
> > Subject: [p4] How to findout changes in the current client
> >
> > Hi Folks,
> >
> > I have a client and want to find out all change numbers (either submitted
> > or
> > pending ) from that client.
> > So far, i was using
> >
> > %p4 changes -c <client name>
> >
> > But looks like I am doing wrong. What if there was client with <client
> > name>
> > and there was few submits in that and
> > and that is deleted and recreated a new client with the same name but no
> > changes (submitted or pending) in the new client (but old name).
> >
> > Any solution?
> >
> >
> >
> >
> -------------------------------------------------------------------------------------------------------------
> > " The only thing worst then losing, is quitting."
> >
> > Your Non Quiting Friend
> > Thandesha V.K
> >
> >
> ----------------------------------------------------------------------------------------------------------------------
> > _______________________________________________
> > 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
> >
> >
> > End of perforce-user Digest, Vol 68, Issue 5
> > ********************************************
> >
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
>
>
>
> --
>
> -------------------------------------------------------------------------------------------------------------
> " The only thing worst then losing, is quitting."
>
> Your Non Quiting Friend
> Thandesha V.K
>
> ----------------------------------------------------------------------------------------------------------------------
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>



-- 
-------------------------------------------------------------------------------------------------------------
" The only thing worst then losing, is quitting."

Your Non Quiting Friend
Thandesha V.K
----------------------------------------------------------------------------------------------------------------------



More information about the perforce-user mailing list