On Sun, 19 Feb 2012 12:53:24 +0100 Bart <[email protected]> wrote:
> On 2/17/12, Graeme Geldenhuys <[email protected]> wrote: > > >>>> just add to the project svn, > >>> > >>> How? > > > > Or read the SVN documentation. It is called the SVN Red Book, and it > > is well written, with lots of examples. > > > > http://svnbook.red-bean.com/ > > > I have read it, but it confuses me. > If I understand correclty when you want to commit, you must always be > working on the latest revision of that particular file. > For a small project like this, I can see that happening. > But most of the time when I'm solving Lazarus bugs, when I'm done > Lazarus is many revisions ahead. That's why you should do svn update before creating the patch. > I prefer submitting patches to the bugtracker and let someone who > actually knows what he is doing (with regards to svn/committing) do > the actual commit. The one has to apply your patch to the head revision. > > Another more versatile option is to use git-svn. That means you work > > with a SVN repository but managed by Git. > > Need a new computer for that. > But basically see my previous remark. Mattias -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
