mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: Chmouel Boudjnah <chmouel@mandrakesoft.com>
Cc: George Anzinger <george@mvista.com>,
	Dan Aloni <karrde@callisto.yi.org>,
	Ivan Passos <lists@cyclades.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Patch generation
Date: Sat, 11 Nov 2000 01:30:48 -0600 (CST)	[thread overview]
Message-ID: <14860.62888.81093.51268@wire.cadcamlab.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0011100051190.31850-100000@callisto.yi.org> <3A0C2813.E7CB42D2@mvista.com> <20001110215628.A28057@wire.cadcamlab.org> <m3u29ff51b.fsf@matrix.mandrakesoft.com>


[Chmouel Boudjnah <chmouel@mandrakesoft.com>]
> 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 know about gendiff (as a Debian user I rarely use RPM).
Anyway I prefer my patch[2] as it's more flexible.  gendiff doesn't let
you pass in other diff options (true, many are not useful in this
context but think about -d, -p, -b and -U).

Peter

[2] again, http://bugs.debian.org/64958
-
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/

      reply	other threads:[~2000-11-11  7:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09 22:46 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
2000-11-11  5:31       ` Chmouel Boudjnah
2000-11-11  7:30         ` Peter Samuelson [this message]

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=14860.62888.81093.51268@wire.cadcamlab.org \
    --to=peter@cadcamlab.org \
    --cc=chmouel@mandrakesoft.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®