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

[Serge E. Hallyn]

Quoting Serge E. Hallyn (serge at hallyn.com):
> Quoting Christian PERRIER (bubulle at debian.org):
> > Quoting Serge E. Hallyn (serge at hallyn.com):
> > 
> > > 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?
> > 
> > I'd prefer option a). The plan should indeed to have a clearer
> > separation between upstream development (where I expect more people to
> > get involved, maybe not particularly interested in Debian packaging)
> > and Debian packaging.
> > 
> > Not sure about the www branch. Not sure indeed that it deserves to be
> > kept (hasn't bene updated for years as far as I know).
> 
> Ok thanks I'll go that route.

All right, I have trees up at

github.com/hallyn/shadow   (original upstream directory)
github.com/hallyn/shadow-debian (debian directory)
github.com/hallyn/shadow-www

I also pushed Eric's userns patchset (plus extra patches I needed) into
branch userns.1 at github.com/hallyn/shadow .

Please let me know if anything is amiss.  I created this using
svn2git, with some manual fixup of branches it didn't quite
get right.  If we're happy with this, we can figure out how to
move it to alioth.

-serge