>
> So recipient has to use patch -p1 (or rename his archive) right?
> Do you tell them or just let'em figure it out?
>
> mv pkg pkg.orig
> diff -pruN pkg.orig pkg
>
> is too dangerous (for the recipient)?
>
patch is very smart. It can figure out what files to patch even if the dir
names have
>
> So recipient has to use patch -p1 (or rename his archive) right?
> Do you tell them or just let'em figure it out?
>
> mv pkg pkg.orig
> diff -pruN pkg.orig pkg
>
> is too dangerous (for the recipient)?
>
patch is very smart. It can figure out what files to patch even if the dir
names hav
* "Martin" == Martin Albert <[EMAIL PROTECTED]> wrote:
Hi,
> So recipient has to use patch -p1 (or rename his archive) right?
> Do you tell them or just let'em figure it out?
You can expect that every developer knows how to use patch and that he
will first inspect the file you sent him before ap
* "Martin" == Martin Albert <[EMAIL PROTECTED]> wrote:
Hi,
> So recipient has to use patch -p1 (or rename his archive) right?
> Do you tell them or just let'em figure it out?
You can expect that every developer knows how to use patch and that he
will first inspect the file you sent him before a
On 31-Jan-2001 Martin Albert wrote:
> Hello!
>
> I'm looking for info/doc/scripts/hints on proper / practical ways to
> submit patches.
>
> Of interest to me is also the proper way to generate a patch to a
> single file - what is the best point in the dir structure to start?
> Toplevel, ../Topl
On Wed, 31 Jan 2001, Sean 'Shaleh' Perry wrote:
> On 31-Jan-2001 Martin Albert wrote:
> > proper / practical ways to submit patches?
>
> what i do is:
> ..
> mv package package.shaleh
> dpkg-source -x package.dsc
> # the N makes it include files I might have added
> diff -pruN package package.sha
Hello!
I'm looking for info/doc/scripts/hints on proper / practical ways to
submit patches.
Of interest to me is also the proper way to generate a patch to a
single file - what is the best point in the dir structure to start?
Toplevel, ../Toplevel, ... ?
But currently i do have fixes for around
On Wed, 31 Jan 2001, Sean 'Shaleh' Perry wrote:
> On 31-Jan-2001 Martin Albert wrote:
> > proper / practical ways to submit patches?
>
> what i do is:
> ..
> mv package package.shaleh
> dpkg-source -x package.dsc
> # the N makes it include files I might have added
> diff -pruN package package.shal
On 31-Jan-2001 Martin Albert wrote:
> Hello!
>
> I'm looking for info/doc/scripts/hints on proper / practical ways to
> submit patches.
>
> Of interest to me is also the proper way to generate a patch to a
> single file - what is the best point in the dir structure to start?
> Toplevel, ../Tople
Hello!
I'm looking for info/doc/scripts/hints on proper / practical ways to
submit patches.
Of interest to me is also the proper way to generate a patch to a
single file - what is the best point in the dir structure to start?
Toplevel, ../Toplevel, ... ?
But currently i do have fixes for around
10 matches
Mail list logo
