Not in CVS yet... I have to get to a different machine to do that...
please make sure, to check it in correctly, it's much easier to find the changes in cvs and merge them into devel_
the changelog hasn't been showing the changes in ./src
thanks ... tim
OK... I uploaded it and re-downloaded it to check it's up to date...
cheers Miller
On Mon, Feb 21, 2005 at 09:58:12AM +0100, Tim Blechmann wrote:
Not in CVS yet... I have to get to a different machine to do that...
please make sure, to check it in correctly, it's much easier to find the changes in cvs and merge them into devel_
the changelog hasn't been showing the changes in ./src
thanks ... tim
-- mailto:TimBlechmann@gmx.de ICQ: 96771783 http://www.mokabar.tk
latest mp3: http://mattin.org/mp3.html
After one look at this planet any visitor from outer space would say "I want to see the manager." William S. Burroughs
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
OK... I uploaded it and re-downloaded it to check it's up to date...
well, the cvs _is_ up to date ... i just think, something strange is going on, since the cvs log doesn't show the changes in ./src ...
i haven't experienced that with my little experience with cvs, but i somehow think, you are doing something else, than committing you changes to stable_0_38 and tagging it ...
cheers ... tim
Aha... I've been "tagging" before "committing" on the assumption that the tag was associated with the checked-out copy. Perhaps "cvs tag" tags the current state of the repository instead. So now that I have to update to 0.38-4 anyway, I'll try the other order.
Miller
On Mon, Feb 21, 2005 at 10:40:46PM +0100, Tim Blechmann wrote:
OK... I uploaded it and re-downloaded it to check it's up to date...
well, the cvs _is_ up to date ... i just think, something strange is going on, since the cvs log doesn't show the changes in ./src ...
i haven't experienced that with my little experience with cvs, but i somehow think, you are doing something else, than committing you changes to stable_0_38 and tagging it ...
cheers ... tim
-- mailto:TimBlechmann@gmx.de ICQ: 96771783 http://www.mokabar.tk
latest mp3: http://mattin.org/mp3.html
After one look at this planet any visitor from outer space would say "I want to see the manager." William S. Burroughs
System: Linux-2.6.10 realtime (gentoo)
pd works in oss, but refuses to start with alsa:
giove ~ # pd -alsa priority 8 scheduling enabled. memory locking enabled. priority 6 scheduling enabled. memory locking enabled. ALSA lib pcm.c:1181:(snd_pcm_link) SNDRV_PCM_IOCTL_LINK failed: File descriptor in bad state pd: pcm.c:942: snd_pcm_prepare: Assertion `pcm->setup' failed. Pd: signal 6 pd_gui: pd process exited
giove ~ # pd -oss priority 8 scheduling enabled. memory locking enabled. priority 6 scheduling enabled. memory locking enabled. ...
what's up?
Oops... it was broken all right. I've put up Pd 0.38-4 to fix it. (other platforms shouldn't be affected.)
Miller
On Tue, Feb 22, 2005 at 12:57:47AM +0100, Federico wrote:
System: Linux-2.6.10 realtime (gentoo)
pd works in oss, but refuses to start with alsa:
giove ~ # pd -alsa priority 8 scheduling enabled. memory locking enabled. priority 6 scheduling enabled. memory locking enabled. ALSA lib pcm.c:1181:(snd_pcm_link) SNDRV_PCM_IOCTL_LINK failed: File descriptor in bad state pd: pcm.c:942: snd_pcm_prepare: Assertion `pcm->setup' failed. Pd: signal 6 pd_gui: pd process exited
giove ~ # pd -oss priority 8 scheduling enabled. memory locking enabled. priority 6 scheduling enabled. memory locking enabled. ...
what's up?
-- Federico
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list