All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: George Anzinger <george@mvista.com>
Cc: Dan Aloni <karrde@callisto.yi.org>,
	Ivan Passos <lists@cyclades.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Patch generation
Date: Fri, 10 Nov 2000 21:56:28 -0600	[thread overview]
Message-ID: <20001110215628.A28057@wire.cadcamlab.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0011100051190.31850-100000@callisto.yi.org> <3A0C2813.E7CB42D2@mvista.com>
In-Reply-To: <3A0C2813.E7CB42D2@mvista.com>; from george@mvista.com on Fri, Nov 10, 2000 at 08:53:39AM -0800


  [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' which lets you specify
your backup suffix, then it just takes one file|dir instead of two.

  diff -urN -Xdontdiff -k.orig {source-tree}

It's been sent to Paul Eggert (of diffutils); no word so far.

[George Anzinger]
> (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)

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-11  3:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09 22:46 Patch generation Ivan Passos
2000-11-09 22:56 ` Chmouel Boudjnah
2000-11-09 22:57 ` Infamous Woodchuck
2000-11-09 23:08 ` Dan Aloni
2000-11-10 16:53   ` George Anzinger
2000-11-10 19:46     ` Dan Aloni
2000-11-10 20:13       ` George Anzinger
2000-11-11  3:56     ` Peter Samuelson [this message]
2000-11-11  5:31       ` Chmouel Boudjnah
2000-11-11  7:30         ` Peter Samuelson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001110215628.A28057@wire.cadcamlab.org \
    --to=peter@cadcamlab.org \
    --cc=george@mvista.com \
    --cc=karrde@callisto.yi.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@cyclades.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.