1 Feb 17:49
Re: using Git/SVN to manage .info files in local/ tree?
Charles Lepple <clepple <at> gmail.com>
2009-02-01 16:49:41 GMT
2009-02-01 16:49:41 GMT
Executive summary: using Git, with three separate repositories. See below for details. On Jan 3, 2009, at 10:40 PM, Charles Lepple wrote: > Note: if you thought this was going to be a rant about keeping info > files in CVS, sorry to disappoint you. > > I have been keeping .info files for my packages in my own SVN > repository for some time now, and IMHO things are working pretty well. > > The one thing that I think could use a little improvement is tracking > when versions have been pushed from my local directory to unstable, > and from unstable to stable (or when another maintainer commits a > change to CVS, and I blindly overwrite that with local changes when > upstream releases a new version). > > Has anyone set up something like this, where you can easily summarize > what packages need to be tested, then promoted? (I know there is > something like this on the PDB for all packages, but I figure this > could most easily be tracked locally, especially since the PDB has no > concept of my local/ directory, and takes some time to update.) > > I know just enough about Git to be dangerous, so if you have more > git-fu please shoot holes in this idea: stable, unstable and local are > all Git repositories (with appropriate ignore rules for both CVS > metadata and packages which I don't maintain). The unstable repository > is cloned from local, and both are seeded with the unstable tree from > CVS (similarly, stable is cloned from unstable, but with the actual > contents imported from CVS).(Continue reading)
RSS Feed