mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: "David L. Parsley" <parsley@linuxjedi.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question on generating a patch
Date: Mon, 8 Jan 2001 23:14:43 -0600	[thread overview]
Message-ID: <20010108231443.B3385@cadcamlab.org> (raw)
In-Reply-To: <3A5A9444.5B2772F2@linuxjedi.org>
In-Reply-To: <3A5A9444.5B2772F2@linuxjedi.org>; from parsley@linuxjedi.org on Mon, Jan 08, 2001 at 11:32:04PM -0500


[David L. Parsley]
> I read the FAQ and SubmittingPatches, but how best to generate a
> patch that moves a file from on dir to another?  diff -urNP makes the
> patch a lot longer than it seems like it should be...

A major weakness of the 'patch' command -- you cannot gracefully move
or rename files.  Larry Wall saw this years ago and invented a hybrid
sort of patch that runs as a shar-like shell script, moving things
around before actually applying itself as a patch.  But most people,
including linux-kernel, don't use lwall's patch+shar format.


- If it's a fairly small file anyway, just use 'diff -urN' and don't
worry about it.

- If it's a large file or several files, or if you are making
significant changes to said files besides moving them, you should
probably list two separate steps: first, describe the rearrangement,
perhaps as a series of 'mv' commands; second, give us a patch against
the new arrangement.


Either way, you need to make it clear what changes, if any, have been
made to a particular file "in transit".  With just 'diff -urN' and no
explanation, it is hard to tell one way or the other.

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/

      reply	other threads:[~2001-01-09  5:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09  4:32 David L. Parsley
2001-01-09  5:14 ` 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=20010108231443.B3385@cadcamlab.org \
    --to=peter@cadcamlab.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parsley@linuxjedi.org \
    /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®