Based on a SVN example, it lists a diff of files under source control that have not been checked in.
So, I guess in my case, it's a sandbox <-> repository comparison. I don't think that the up stream diff comes into it. Unless the git implementation does something totally different when it has something to push to??? -Chris On Thu, Feb 23, 2012 at 5:16 PM, Chris Graham <chrisgw...@gmail.com> wrote: > Hi All. > > How is this meant to work? > > Specifically, for a distributed type of vcs, what am I comparing? What to > what? > > In Jazz, I have a sandbox, that is on your local PC. > > On the server we have a repository workspace (that is just ours), and > we checkin to that, or checkout (load) from that. > > no body else sees that. > > then, if we have a flow target defined, when we are ready, we deliver > (up) or accept. This would be the equivalent of a git push/pull > respectively. I'm using the pushChanges flag to control the upstream > deliveries - like git. > > So, what do I perform the diff against? > > NOTE: There may not be a flow target (a user may not have a stream [or > other workspace] to deliver too). > > sandbox to workspace ? - which effectively only does a diff on what > has not been checked in. > > sandbox to stream (if it exists) - which shows what has not been delivered. > > ???? > > -Chris > > PS: What uses the scm:diff command ? Or is it a nice to have? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
