Hans-Christoph Steiner wrote:
As for 'scripts', there needs to be a place for all the scripts needed to
build Pd-extended. Whether that's also the place for bash_completion,
etc, that's a separate question.
but since it is the pd-repository rather than the pd-extended
repository, it
Hans-Christoph Steiner wrote:
#TAGS:misc
import (htdocs pd-msg aenv~ bsaylor susloop~ svf~ vadsr~ xgui zhzxh~)
These tags are useful for handling imported code that is maintained
elsewhere.
thats what the documentation says.
have you ever made any use of the useful thing?
Does SVN
Hello,
I just missed the pdconv, so how is the authorization for the repository
planed ? Is it possible to restrict access to a subfolder ?
If so I would recommend to put the trunk, tags, branches as subfolder of
projects which can be deligated rather then have a very long list of versions
Winfried Ritsch wrote:
Hello,
I just missed the pdconv, so how is the authorization for the repository
planed ? Is it possible to restrict access to a subfolder ?
no, since the plan is to stay with sourceforge for now, there is still
no way to restrict write access to submodules (afaik).
hello,
I just missed the pdconv, so how is the authorization for the repository
planed ? Is it possible to restrict access to a subfolder ?
no, since the plan is to stay with sourceforge for now, there is still
no way to restrict write access to submodules (afaik).
If so I would
On Sep 12, 2007, at 5:26 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
I say go to town with the docs, they could definitely use some
cleanup
just for the non-natives among us: what does go to town with the
docs mean?
Oops, sorry, I could have also said go crazy with,
Hallo,
IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
personally i think externals is exactly the name: it means pd stuff
that does not come with pd itself, rather than pd-objects written in C
How about extensions? Somehow the word externals has sunken in as
meaning binary
On 12/09/2007, at 20.50, Frank Barknecht wrote:
IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
personally i think externals is exactly the name: it means pd
stuff
that does not come with pd itself, rather than pd-objects
written in C
How about extensions? Somehow the
Hallo, yes. The appropriate way to handle this IMO is to do the initial
conversion (thus creating the many directories), then do an svn rm for those
tags that are abandoned or unnecessary. Tags and Branches in SVN are great
because they can have lifetimes - you can make your branch to try some
On Sep 12, 2007, at 4:07 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
Sounds good, how about downcasing while you are at it, so we have
it more standardized.
i don't see a real benefit from it.
but then: why not?
(and finally: since Framestein is really abandoned for
On Sep 12, 2007, at 4:22 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
#TAGS:misc
import (htdocs pd-msg aenv~ bsaylor susloop~ svf~ vadsr~ xgui
zhzxh~)
These tags are useful for handling imported code that is
maintained elsewhere.
thats what the documentation says.
Does SVN handle this differently?
yes and now.
yes: you don't _have_ to create a tag and a branch whenever you
import code.
no: you can import code that is maintained elsewhere into a branch,
a tag, the trunk (or just any other directory)
yes: svn is able to handle references to
12 matches
Mail list logo
