[PATCH] coccinelle: misc: minmax: suppress patch generation for err returns

2021-04-09 Thread Denis Efremov
There is a standard idiom for "if 'ret' holds an error, return it": return ret < 0 ? ret : 0; Developers prefer to keep the things as they are because stylistic change to "return min(ret, 0);" breaks readability. Let's suppress automatic generation for this type of patches. Signed-off-by

Re: Patch generation

2000-11-10 Thread Peter Samuelson
[Chmouel Boudjnah <[EMAIL PROTECTED]>] > i would recommend to use the orig.el[1] from frederic.lepied with > Emacs, it save any files before editing with a particuliar prefix I'll take a look, thanks. > and you can generate the patch with the gendiff script (included with > rpm). I did not kno

Re: Patch generation

2000-11-10 Thread Chmouel Boudjnah
Peter Samuelson <[EMAIL PROTECTED]> writes: > > (I prefer EMACS, which likes to unlink.) > No it doesn't, not always. Your choice: > (setq make-backup-files nil) > (setq backup-by-copying t) i would recommend to use the orig.el[1] from frederic.lepied with Emacs, it save any files before ed

Re: Patch generation

2000-11-10 Thread Peter Samuelson
[Dan Aloni] > > Then you run this script (I got it when Riel pasted it on IRC) > > > > for i in `find ./ -name \*.orig` ; do diff -u $i `dirname $i`/`basename $i > > .orig` ; done That works, but see http://bugs.debian.org/64958 for my variant: a fairly trivial diff diff that adds a flag '-k'

Re: Patch generation

2000-11-10 Thread George Anzinger
Dan Aloni wrote: > > On Fri, 10 Nov 2000, George Anzinger wrote: > > > > 4 kernel trees, one after make dep ; make bzImage, and all taking together > > > just 193MB, instead of about 400MB... hard links, gotta love'em. > > > > Ok, this is cool, but suppose I have the same file linked to all thes

Re: Patch generation

2000-11-10 Thread Dan Aloni
On Fri, 10 Nov 2000, George Anzinger wrote: > > 4 kernel trees, one after make dep ; make bzImage, and all taking together > > just 193MB, instead of about 400MB... hard links, gotta love'em. > > Ok, this is cool, but suppose I have the same file linked to all these > and want to change it in al

Re: Patch generation

2000-11-10 Thread George Anzinger
Dan Aloni wrote: > > On Thu, 9 Nov 2000, Ivan Passos wrote: > > > Where in the src tree can I find (or what is) the command to generate a > > patch file from two Linux kernel src trees, one being the original and the > > other being the newly changed one?? > > The syntex looks like this one: >

Re: Patch generation

2000-11-09 Thread Dan Aloni
On Thu, 9 Nov 2000, Ivan Passos wrote: > Where in the src tree can I find (or what is) the command to generate a > patch file from two Linux kernel src trees, one being the original and the > other being the newly changed one?? The syntex looks like this one: diff -urN old_tree new_tree > your_

Re: Patch generation

2000-11-09 Thread Chmouel Boudjnah
Ivan Passos <[EMAIL PROTECTED]> writes: > Where in the src tree can I find (or what is) the command to generate a > patch file from two Linux kernel src trees, one being the original and the > other being the newly changed one?? > I've tried 'diff -ruN', but that does diff's on several files that

Re: Patch generation

2000-11-09 Thread Infamous Woodchuck
On Thu, 9 Nov 2000, Ivan Passos wrote: > Where in the src tree can I find (or what is) the command to generate a > patch file from two Linux kernel src trees, one being the original and the > other being the newly changed one?? > > I've tried 'diff -ruN', but that does diff's on several files tha

Patch generation

2000-11-09 Thread Ivan Passos
Hello, Where in the src tree can I find (or what is) the command to generate a patch file from two Linux kernel src trees, one being the original and the other being the newly changed one?? I've tried 'diff -ruN', but that does diff's on several files that could stay out of the comparison (such