hello Paul,
Paul Gevers writes:
> On 03-04-15 17:55, Felix Natter wrote:
>> does nobody have an opinion on this?
>>
>> In short: Is it better to have _a lot_ of beta gbp import-origs, commits
>> that are reverted/superceded etc. OR
>> develop on a private repository and copy the debian/* changes
On 03-04-15 17:55, Felix Natter wrote:
> does nobody have an opinion on this?
>
> In short: Is it better to have _a lot_ of beta gbp import-origs, commits
> that are reverted/superceded etc. OR
> develop on a private repository and copy the debian/* changes to alioth
> on a release?
If this means
Felix Natter writes:
> hello mentors,
Dear mentors,
does nobody have an opinion on this?
In short: Is it better to have _a lot_ of beta gbp import-origs, commits
that are reverted/superceded etc. OR
develop on a private repository and copy the debian/* changes to alioth
on a release?
Thanks a
hello mentors,
my workflow with more complex packages is that I start early and push
the packaging (branching off the current alioth stable version) to
github.com/fnatter/foo-debian-unstable, where I import almost every
beta, fix the problems that occur and push the result to github.
That way, my
4 matches
Mail list logo
