[Pkg-shadow-devel] [PATCH 00/11] pkg-shadow support subordinate ids with user namespaces

Serge E. Hallyn serge at hallyn.com
Wed Jun 5 04:26:29 UTC 2013


Quoting Christian PERRIER (bubulle at debian.org):
> Quoting Serge E. Hallyn (serge at hallyn.com):
> 
> > Hi,
> > 
> > I've not used svn at all, but would it help if I take a shot at this
> > conversion (maintaining full history) putting the result into github
> > for a first run?
> 
> Why not?
> 
> At first glance, I'd rather keep the "official" copy on
> alioth.debian.org though I would indeed be delighted (as Debian
> maintainer) if someone else steps in to take "upstream" development
> over so that I can stick with Debian packaging.

Hi,

at github.com/hallyn/shadow is the simple, dumb result of doing a
'git svn clone'.  It kept the svn branch directory layout which is
not ideal.  However, since there are different branches for upstream,
debian, and www, converting to git branches isn't entirely straightforward.
Should we

 (a) turn this into three git trees, with proper git branches
     in each, so that for instance upstream/tags/4.1.5.1/* would be in
     (tagged) branch 4.1.5.1 of shadow-upstream/, and upstream/trunk/* would
     be master branch of shadow-upstream,
 (b) keep the svn style directory layout,
 (c) keep one tree with one named branch for every branch that exists in
     any of the trees, and for instance shadow/upstream/ would be empty for
     branch 'etch' (which only exists for debian)?
or
 (d) do something more clever?

-serge



More information about the Pkg-shadow-devel mailing list