Howdy, I have more questions already!
I am seeing *lots* of tags on the Parrot subversion server that are not releases, a whole bunch called reconfigure-\d+ and buildtools-\d+ . Do we want to move all these to git, or do we only want release tags in git? If none of these tags are wanted, we should removed them from the subversion server, so that no special case code is needed in the mirror script. Duke On Sat, Aug 21, 2010 at 10:32 AM, Jonathan Leto <[email protected]> wrote: > Howdy, > > I have been working on a github mirror of the Parrot subversion repo > [0], and here are some questions that I have: > > 1) How do we want to deal with tags? Subversion "tags" are actually > just branches. Should I turn all subversion tags in git branches? > I have been thinking of putting them into a "namespace", purely for > organizational reasons, so each subversion tag would become a branch > named something like > > tags/RELEASE_X_Y_Z > > in git. > > 2) I could also create proper git tags for each subversion tag. Would > this be preferred? Does anybody actually want subversion tags to be > branches? > > I am sure I will have more questions, any feedback I can get about > these questions, as well as other requests about our github mirror, > would be greatly appreciated! > > Duke > > [0] http://github.com/parrot/parrot > > > > -- > Jonathan "Duke" Leto > [email protected] > http://leto.net > -- Jonathan "Duke" Leto [email protected] http://leto.net _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
