Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Mar 1995 08:58:19 +0100 (MET)
From:      J Wunsch <j@uriah.heep.sax.de>
To:        chaos@rivers.oscs.montana.edu (Jason Boerner)
Cc:        PVinci@ix.netcom.com, hackers@FreeBSD.org
Subject:   Re: [Q] best way to submit patches/changes?
Message-ID:  <199503230758.IAA17467@uriah.heep.sax.de>
In-Reply-To: <Pine.ULT.3.91.950323003546.14857G-100000@rivers.oscs.montana.edu> from "Jason Boerner" at Mar 23, 95 00:36:14 am

next in thread | previous in thread | raw e-mail | index | archive | help
As Jason Boerner wrote:
> 
> Dito... If all that you want is a diff output, how should it be generated?

cd /usr/src/where/it/lives
diff -c file.orig file > /tmp/my.contribu.tion

or
cd /usr/src
diff -c where/the/first/one/lives/file.orig where/the/first/one/lives/file \
  > /tmp/my.contribu.tion
diff -c where/another/one/lives/file.orig where/another/one/lives/file \
  >> /tmp/my.contribu.tion

The sequence (first file: .orig, second file: new one) is important
to avoid confusion.

You can also replace the ``-c'' by a ``-u'' (unified context diff),
making the diff smaller.

Be sure to specify what version the patch is against.  Either ``2.0
RELEASE'', or specify the $Id$ strings of the source files.  Telling
``-current as of Foocember 5th'' is too imprecise.  (Even
``2.0-950210-SNAP'' is problematically, since the tree has not been
tagged for the SNAPs.  Yes, i'm guilty of this one, too. :)

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503230758.IAA17467>