-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On May 22, 2008, at 11:17 PM, Charles Albrecht wrote:
On May 22, 2008, at 5:21 PM, Timothy Stone wrote:
I'm not sure, if I was BB, that I would even consider this...
reason: the setup described above, and in the original post, is
"not ideal at all," but not at all what CVS or SVN, or PVCS, or /
insert SCM here/ expects. Nor, is it any documented, or recommended
project management pattern.
To Matthias, I would ask, "Why are you being constrained to one
directory?" What is preventing you from have a "work" directory,
under which there is a "svn/project_name" and "cvs/project_name"
directory? It is an automated build process? What sort of project
would want you to use two different SCM repositories.
This is something I do on a daily basis, and if there is something
that I can assist with, I only need to know more about what you are
doing to provide some direction.
The usage pattern for this is the private versioning pattern (ref http://www.scmpatterns.com/book/pattern-summary.html)
in which you essentially version all of your local "off-code-line"
work independently from the source codeline. This sounds like what
Matthias is looking to implement.
I'm not sure that Matthias is describing a "pattern," but a problem.
He is describe a single folder with multiple SCM code branches...
work/
.svn <----- meta-data files for each SCM
CVS <----- CVS may be seeing some of these as "new" or "added"
project1-file
project1-dir
.svn
...
project2-file
project2-dir
CVS
...
Matthias is possibly having some conflict in the each SCM system meta-
data. And SVN is doing a better job than CVS in filtering out the
other's meta-data files and directories.
I'm not sure the Private Version Pattern applies here. (I'm hoping we
are not getting to derailed from Matthias's problem.) Matthias would
be better helped if he "checked out" his code to specific directories
under "work"
work/
project1
.svn <----- meta-data
project1-file
project1-dir
.svn
...
project2
CVS <----- meta-data
project2-file
project2-dir
CVS
...
...
This is why I said that BB would not be served by attempting to manage
this in the BBEdit code. This is a SCM user experience, or SCM system,
issue; not a BB should fix BBEdit problem.
HTH,
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFINpjNlNb2aYI3YNkRAs3FAJ9zucQblQLUgmSjUOThBdm28jaD2ACeMPkz
GuSrClSv8y+PQA4vth77+qk=
=Ezk/
-----END PGP SIGNATURE-----
--
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
If so, please send mail to <[EMAIL PROTECTED]>, not to the list.
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>
To unsubscribe, send mail to: <[EMAIL PROTECTED]>
