status code philosophy
From: Ben Collins-Sussman <sussman_at_newton.collab.net>
Date: 2000-11-16 05:44:37 CET
Right now we're tracking each working copy file's text and properties
(This was Jim's excellent idea: rather than looking at timestamps to
But I digress.
Because each file has two parts, we have two independent status codes
* Don't show both status codes unless the user explicitly asks for
* It's okay to show both codes if local mods are detected on a file's
QUERY 1: Does this make sense to people?
Btw, here's an example of the status codes in action, as an example:
===============
-- 9 ( none ) tests/t1/iota
Then after editing this file's properties, I see
-M 9 ( none ) tests/t1/iota
Then when I update again and get a conflicting property, I see
-C 11 ( none ) tests/t1/iota
If I edit iota's text, I see
MC 11 ( none ) tests/t1/iota
And then if I delete the ".prej" file sitting next to iota, Subversion
MM 11 ( none ) tests/t1/iota
================
QUERY 2: Will we ever see anything other than a '-' in the first
Directories have genuine properties, so the second status code may
Here's one idea: if I `svn add` a file to a directory, has the
I'd like to hear if people think this is sound reasoning.
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.