On Jul 9, 2007, at 11:25 PM, Chris McCormick wrote:
On Mon, Jul 09, 2007 at 07:49:29AM -0400, Hans-Christoph Steiner wrote:
Well as it stands now I'd have the annoying requirement that I keep two local copies of s-abstractions and have to manually port changes between them and commit to two different repositories, which was the reason for my original post.
If you are going to maintain your code in a repository that is different from the pure-data one, then it makes the most sense to only import releases into the pure-data CVS, instead of keeping it synced. "cvs import" allows you to do this with one command that also makes a tag for that release.
Ok, I'm convinced. I haven't used CVS import like that before; I wonder if you could point me to some docs on that, or give me an example. Would it be something like:
export CVSROOT=chr15m@pure-data.cvs.sourceforge.net:/cvsroot/pure-data cvs login cvs import s-abstractions/
More like this:
export CVSROOT=:ext:chr15m@pure-data.cvs.sourceforge.net:/cvsroot/ pure-data export CVS_RSH=ssh cd s-abstractions cvs import abstractions/s-abstractions CHR15M S-ABSTRACTIONS_0_2
It goes like this: cvs import repository vendor-tag release-tags...
repository - the full path to the spot in the CVS repository where this stuff will go. This could be instead: externals/s-abstractions, abstractions/chr15m/s-abstractions, etc. etc.
vendor-tag - whatever tag you want for yourself, standardized to UPPERCASE
release-tags - a tag for the library and version that you are importing (multiple if you want, only one required)
.hc
Best,
Chris.
------------------------------------------------------------------------ ----
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.