[p4] Re: determining the status of a clientspec - Chuck Karish - com.perforce.perforce-user

7 messages in com.perforce.perforce-user[p4] Re: determining the status of a ...

From	Sent On	Attachments
Dennis Wheeler	09 Oct 2001 15:16
Jeff A. Bowles	09 Oct 2001 16:14
Rick Macdonald	09 Oct 2001 16:30
Dennis Wheeler	09 Oct 2001 17:24
Marc Unangst	09 Oct 2001 19:13
Chuck Karish	09 Oct 2001 23:28
Jeremy Russell	10 Oct 2001 09:46

Subject:	[p4] Re: determining the status of a clientspec
From:	Chuck Karish (kar...@well.com)
Date:	10/09/2001 11:28:49 PM
List:	com.perforce.perforce-user

At 10:13 PM 10/9/2001 -0400, Marc Unangst wrote:

Developer A: Hmm, I'm seeing a bug where you trip an assert at line X of file
Y.c. Developer B: That's weird, I thought I fixed that. <runs some "p4 changes"
commands> Yup, that's fixed in change 12345. Do you have that? Developer A: Er, I dunno. Let me sync and try again.

I realize that "highest change number" isn't foolproof, but in the presence of
"normal" developer work habits (i.e.,people that sync to head-of-line rather
than to a particular change number, and who sync their whole client at once) it
seems like a good first approximation to answer the question "have you sync'd
since change 12345 was checked in?".

There's a good reason why it's "normal": in most cases, that's the way the development process is organized. The head revisions are supposed to be the latest and greatest from all contributors.

If this weren't the case - a maintenance line accumulating strictly- gated bug fixes, a manifest-managed line made up of individually- enabled changes - the response from Developer B wouldn't make sense. There's a strong resumption that getting the latest changes means being at the state of the product.