Re: topgit patches

also sprach Uwe Kleine-König [off-list ref] [2009.02.26.1515 +0100]:

If you need help, I'm also interested to co-maintain the debian
package. Just an offer ...  (I don't know the exact way to become
a maintainer, if I need to meet a Debian developer, that's no
problem, I know one.)

The Debian package is pretty trivial to maintain on top of upstream
(thanks to topgit), and I am using it a bit as a test-case for
workflow experiments. However, if you are interested in packaging,
by all means, join me. In that case I'd suggest that you make the
0.6-1 Debian package after 0.6 is out, and I give you some hints up
front and then simply stand by to help out.

 1 move all or most topgit-topic-branches to a private namespace, say
   refs/top-heads because the patch branches pollute the output of git
   branch.

But aren't the topic branches essentially also plain Git branches?

 2 export method that works like the existing linearize but creates
   branches for topgit branches living in refs/heads and merges these
   properly without linearisation.
   (obviously depends on 1)

I am not sure I understand what you are trying to do.

 3 address topgit bugs on bugs.debian.org

Awesome. I will try to be available for any support you might need.
I just can't come up with a sufficiently long stretch of time to see
through the next release right now.

Cheers,

-- 
 .''`.   martin f. krafft <madduck@d.o>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
ubuntu is an ancient african word meaning "i can't install debian."
                                                          -- unknown