On Wednesday 01 October 2008 17:54:24 Manoj Srivastava wrote:
--cut--
> > 1) people do not need quilt nor dpkg to view and apply these patches
>
> I find it easier reading code than reading patches upon patches
> upon patches that modify code I can read. If there are dependent
> patches,
On Wed, Oct 01 2008, George Danchev wrote:
> Quoting Manoj Srivastava <[EMAIL PROTECTED]>:
>
>> On Wed, Oct 01 2008, martin f krafft wrote:
>>
>>
>>> Assuming we have a number of feature branches, we may well have to
>>> resolve conflicts among them, so an integration branch seems like
>>> the rig
Quoting Manoj Srivastava <[EMAIL PROTECTED]>:
> On Wed, Oct 01 2008, martin f krafft wrote:
>
>
>> Assuming we have a number of feature branches, we may well have to
>> resolve conflicts among them, so an integration branch seems like
>> the right way forward. So unless we just build the package f
On Wed, Oct 01 2008, martin f krafft wrote:
> Assuming we have a number of feature branches, we may well have to
> resolve conflicts among them, so an integration branch seems like
> the right way forward. So unless we just build the package from the
> integration branch to produce a monolithic p
also sprach Teemu Ikonen <[EMAIL PROTECTED]> [2008.10.01.1243 +0200]:
> I thought about this some more and indeed there are problems.
> Generating patches based on just one tag in the integration branch
> probably would work when all the topic branches are still alive (i.e.
> there is a head ref wh
On Wed, Oct 1, 2008 at 11:38 AM, martin f krafft <[EMAIL PROTECTED]> wrote:
> also sprach Teemu Ikonen <[EMAIL PROTECTED]> [2008.09.30.2329 +0200]:
>> At the moment, yes, but the new dpkg with version 3.0 quilt format
>> builds the source package from sources with the patches applied.
>> This enabl
