[RFC] Switching glibc-bsd from svn to git

Hi! I'd like to propose switching and splitting the glibc-bsd repo from svn to git repositories, because svn is increasingly painful compared to git, when it comes to at least partial commits, tagging (we don't seem to be tagging much), branching and merging, offline hacking, etc... I'd even volu

Re: [RFC] Switching glibc-bsd from svn to git

Hi Guillem, (swapping some sentences) > What do people think? Yes! Please do! I made the same proposal a while back and I'm looking forward to see that happen. > I'd even volunteer to switch the repositories, although I'd like to > keep just the current packaging-only structure, to the point I'

Re: [RFC] Switching glibc-bsd from svn to git

Hi! Guillem Jover writes: > I'd like to propose switching and splitting the glibc-bsd repo from svn > to git repositories, because svn is increasingly painful compared to git, > when it comes to at least partial commits, tagging (we don't seem to > be tagging much), branching and merging, offline

Re: [RFC] Switching glibc-bsd from svn to git

Hi Guillem! This sounds like a good idea. Git would seem easier to work with, for exactly the things you mentioned. I still think it is best to fetch upstream source using Subversion; but certainly we are free to choose something else for the packaging. Regards, -- Steven Chamberlain ste...@p

Re: [RFC] Switching glibc-bsd from svn to git

I'd like to propose switching and splitting the glibc-bsd repo from svn to git repositories My position: - use svn or git It does not matter for me. - packaging-only or full content I strongly prefer packaging-only. - one common repository x repository per package I slightly prefer one