Hiya everybody,
I've recently converted my opencbm[1] package to TopGit, adopting a
workflow similar to that suggested by Martin. The main difference is
that instead of maintaining a separate long-lived build branch, I'm
exporting all patches directly on master.
Maybe it's just me, but I can't
On Tue, May 05, 2009 at 03:18:51PM -0400, Frédéric Brière wrote:
I've recently converted my opencbm[1] package to TopGit, adopting a
workflow similar to that suggested by Martin. The main difference is
that instead of maintaining a separate long-lived build branch, I'm
exporting all patches
Let's say I've once created the topic branch fixes/foo, which has now
been incorporated in the latest upstream release. What is the best way
of dealing with this now-obsolete branch? (Let's pretend for
simplicity's sake that it is not part of any other branch's base.)
Am I right to assume that
also sprach Frédéric Brière fbri...@fbriere.net [2009.05.05.2118 +0200]:
Maybe it's just me, but I can't see the point in having a dedicated
long-lived[2] build branch separate from master anymore.
The point for me is inherent in #500656: to be able to obtain the
source tree for a package in
On Tue, May 05, 2009 at 09:59:01PM +0200, martin f krafft wrote:
also sprach James Vega james...@debian.org [2009.05.05.2135 +0200]:
Files that are purely a result of the final integration (like
debian/changelog, debian/NEWS, and debian/patches/*) only exist in the
integration branch. This
