Thierry Randrianiriana <thie...@debian.org> wrote: > Hello, > > You can improve php-elisp package via collab-maint : > > http://svn.debian.org/wsvn/collab-maint/ext-maint/php-elisp/ > > I think that it's better if you co-maintain this package with me. > You're welcome!
Thanks for the invitation Thierry. I don't use PHP so I'm not really sure that I want to go that far. But maybe... I have used CVS for years, tried to use svn once for proj co-maintenance and failed to understand it, but have since been using git (for gri and gri-mode.el) and bzr (for MH-E in the central Emacs repo). Maybe I missed something the first time around (like the concept of pushing changes back). But I recall it kept all revision separate in subdirectories. How would I (1) checkout php-elisp, (2) edit a change, (3) possibly add a subdirectory for patches, (4) commit and push it back, and (5) build a package? (1) From http://svn.debian.org I deduced the checkout as: $ svn checkout svn://svn.debian.org/collab-maint/ext-maint/php-elisp But that gives me only the debian directory. Where do you keep the upstream file? Or do you build that separately and just copy your debian directory to this repo? (2) I guess I would just edit a file now, there's no `svn edit' command. (3) adding a file or a directory is simply with "svn add file", right? (4) does "svn commit" push changes back to the repo? Or is it local? (5) are you using package building tools specific to svn? Peter -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
