Re: [Audacity-devel] Equalizer problem - Fixed (mostly)
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Markus M. <me...@me...> - 2005-07-07 08:45:37
|
Hi Martyn, thanks for providing the source to the fixes. I will have a look at it and merge it into the development version of Audacity as soon as possible. Some words to CVS: CVS is a version control system for collaboration of development. It provides the source files of a program on a central server (in our case SourceForge.net). All source files together form a so-called "repository". If you download the source files from the server this is called "checking out the repository". When you upload changes to the source files you made locally on your computer, this is called "committing to the repository". With Audacity (as with many other free software projects), everyone can check out the repository, but only a few people can commit changes. Every file in the repository can have different versions (called "revisions"). That is, if someone commits a change which contains a bug, I can say to the repository "go back to the state you had a week ago". Also important for you: The Audacity CVS repository currently contains two different so-called "branches". These are two independent versions of the software and could be seen as two different repositories. The "HEAD" branch contains the very most recent development and will form the base for the upcoming 1.3 beta release. You will automatically get the HEAD branch when you don't say otherwise to CVS. The "AUDACITY_1_2" branch has formed the base for 1.2.x series. No new development is done on this branch, only bug fixes. So why should you use CVS? The reason is that with CVS you can create so-called "diffs". Those are small files which describe exactly what you have changed since you last checked out your local copy of the CVS repository. So if you want to fix a bug in, say, the HEAD branch, just check out the HEAD repository, fix and test your bug, then create the diff and send it to the Audacity list. Someone with write access to the repository will then apply (sometimes called "merge") the diff, which is often also called a "patch", to the repository. This is an automatic procedure and is much faster than manually replacing files. Another good thing is that patches (diffs) still work, when someone else has changed the repository in the meantime (and if they don't you'll get a meaningful error message at least). I agree with Lynn that it is possible to use CVS from the command line (I do this on Linux), but with TortoiseCVS there's really no need to. Just choose "CVS Checkout" from the menu and enter the line with the ":pserver:" on it, and it will work. You may also want to do a regular "CVS Update" to keep your local copy synchronized with the repository on the server (so you will automatically get all the new features). The creation of a diff is also a simple menu command in TortoiseCVS. Hope that helps you to get started. Markus Mar...@ao... schrieb: > Markus > > I think I have put all the files changed into a zip at > http://members.aol.com/MartynShaw/fixes.zip . Can you get it from > there and do the diff thing for me? I would try and do the cvs method > but I'm not sure how I got the files from CVS in the first place and I > think I may have added various bits from here and there also and > changed things in previous compilation experiments so any diff may > include lots of spurious stuff. > > I think I got it from CVS using WinCVS (which I struggled with) but I > don't remember how, I think it was in January. > > I would like to start again with CVS and my whole environment. What > is the meaning of HEAD? Is it the most up to date version? > > If it's easier I will learn how to use CVS (from the suggestion of > using TortoiseCVS) and reapply my fixes. I think I have a project > coming up to recover audio from loads of archive material and so > Audacity may come in useful, particularly CleanSpeech. > > TTFN > Martyn > > In a message dated 06/07/2005 14:49:10 GMT Standard Time, > me...@me... writes: > > Hi Martyn, > > which version of Audacity did you download and change? If it is the > source code of Audacity from the website just send me all the > files (*.h > and *.cpp) you have changed, so I'll just create the patch for > you. If > you have used CVS you can create the diff yourself by issuing the > command "cvs diff -u" in your main directory. > > > Markus > > mar...@ao... schrieb: > > > Markus > > > > I'm afraid that I don't know how to do this and I am not very > familiar > > with CVS and don't know how to make a patch file. Is there a page > > telling me how to do it somewhere? > > > > Martyn > > > > -----Original Message----- > > From: Markus Meyer <me...@me...> > > To: aud...@li... > > Sent: Wed, 06 Jul 2005 08:49:05 +0200 > > Subject: Re: [Audacity-devel] Equalizer problem - Fixed (mostly) > > > > Hi Martyn, > > > > this is awesome!! Do you have a patch file against CVS HEAD for > that, > > so I can integrate it? > > > > Markus > > > > > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies > > from IBM. Find simple to follow Roadmaps, straightforward articles, > > informative Webcasts and more! Get everything you need to get up to > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > _______________________________________________ > > Audacity-devel mailing list > > Aud...@li... > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Audacity-devel mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > |