Jeff, yes but it seems like drinking from a firehose since it prints everything about every file. Even better IMO is the opened command. I just discovered it this evening and it appears to do everything the status operation requires.
mike -----Original Message----- From: Jeff Jensen [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 23, 2005 7:14 PM To: scm-dev@maven.apache.org Subject: RE: provider operations Mike, Are you aware of the fstat command? Thankfully Perforce does not store that data locally, so it does not have to traverse the local directory structure (slower operation). The fstat command has a lot of flexibility to get that info from the server. -----Original Message----- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 23, 2005 9:23 AM To: scm-dev@maven.apache.org Subject: RE: provider operations Status - Perforce does not keep any local metadata next to the files (a la CVS or .svn) so it does not have easy or efficient support to say "give me the status for all changed files below this directory". It keeps that info in one or more changelists associated with the user. I will have to parse those changelists, look for files whose location starts with the current repository path and return those. Update - that should be straightforward then. It seems that Checkout and Update are basically the same operation in Perforce. Thanks for the explanation. mike -----Original Message----- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 23, 2005 4:37 AM To: scm-dev@maven.apache.org Subject: Re: provider operations Doc is actually only in ScmProvider javadoc. Status command returns the status of files in working copy, it's useful to know if a file is modified locally and not committed. Do you have an equivalent in Perforce? Update command update all files in working copy with latest version of files that exists in scm repository. This command use internally in maven-scm the changelog command. Emmanuel Mike Perham a écrit : > Is there a high-level description of WHAT each operation is intended > to provide? I'm trying to map Perforce onto these operations which > were obviously designed for use with svn/cvs and struggling with the > mismatches in the way the systems work. Mostly with update and status. > Can someone in the know shed a little light on what these operations > should do? > > mike > > >
