James Vega wrote:
> From my perspective, it's still worthwhile. The build branch is where
> integration of all changes to the upstream package happens. This
> includes pulling in the packaging changes (aka, debian/) which happens
> on the master branch.
Ah, I see. Basically, your build branch
martin f krafft wrote:
> See #505303. This is also not yet implemented, but pasky worked out
> the logic in the referenced URL
> http://thread.gmane.org/gmane.comp.version-control.git/95858
Yeah, I remember seeing this. His merging made me dizzy. :)
I don't think this addresses the same issue,
(Grr, I'd forgotten how Gmane silently loses posts the first time.)
martin f krafft wrote:
> … the thought of having debian/patches/* with a given patch foo
> inside the topic branch that creates foo just seems sort of, uh,
> cyclical to me, even though (Top)Git won't care as long as you don't
I
also sprach Frédéric Brière [2009.05.06.2049 +0200]:
> Given what I previously said about all debian/* topic branches
> falling behind as soon as I commit something to master, I'm
> considering basing them off the upstream branch. After all,
> there's no technical reason for basing them off maste
also sprach Frédéric Brière [2009.05.06.2016 +0200]:
> I don't think this addresses the same issue, though. This is about
> making sure that a topic branch can be safely deleted even when other
> branches depend on it. IOW, it's purely a TopGit issue.
>
> My concern is what to do once the above
also sprach Frédéric Brière [2009.05.06.1940 +0200]:
> Ah, I see. Basically, your build branch is not TopGit-specific, but is
> an integral part of your workflow. In that case, it certainly makes
> sense to export your patches there. But am I right in assuming that you
> would still maintain a
martin f krafft wrote:
> > (OTOH, I'm not particularly looking forward to having even more
> > top-* refs that I'll forget to push...)
>
> You know you can set it up to auto-push, right? ;)
Unfortunately, any Push line will turn off the default ":" behavior.
So, I either have to maintain a list o
martin f krafft wrote:
> > tg-cleanexport. As I said, I would either need to keep the (empty)
> > topic branch around forever, or override TG_BRANCHES forever, no?
>
> I think as soon as a branch is folded in the way pasky suggests, the
> TopGit diff would be empty, and tg-export knows not to dum
