9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.att.com jmk@plan9.att.com
Subject: format for source diffs
Date: Sun, 20 Aug 1995 23:25:26 -0400	[thread overview]
Message-ID: <19950821032526.SWZ-VjxubR1Cke8zDGxfmTTOUEXFRj_wMroHP0Bkycw@z> (raw)

i can't say i'm thrilled about either of those options.

------ original message follows ------

>From cse.psu.edu!9fans-outgoing-owner Sun Aug 20 10:35:54 EDT 1995
Received: by colossus.cse.psu.edu id <45565>; Sun, 20 Aug 1995 10:25:06 -0400
Received: from galapagos.cse.psu.edu ([130.203.2.12]) by colossus.cse.psu.edu with SMTP id <45561>; Sun, 20 Aug 1995 10:24:50 -0400
Received: from localhost by galapagos.cse.psu.edu with SMTP id <12684>; Sun, 20 Aug 1995 10:24:54 -0400
To:	9fans@cse.psu.edu
Subject: Re: format for source diffs 
In-reply-to: Your message of "Sun, 20 Aug 1995 00:09:29 EDT."
             <95Aug20.005926edt.46381@colossus.cse.psu.edu> 
Date:	Sun, 20 Aug 1995 10:24:41 -0400
From:	Scott Schwartz <schwartz@galapagos.cse.psu.edu>
Message-Id: <95Aug20.102454edt.12684@galapagos.cse.psu.edu>
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu

jmk@plan9.att.com writes:
| I'd like to make the source changes for aux/vga available, what should the 
| format be?

The bundle plus diff would work, but it might be nice to take advantage
of patch's functionality, since most people will be using it anyway and
it can automatically create new files from context diffs built with -Nc
or -Nu.  That would require augmenting /bin/diff or porting gnu diff,
of course.








             reply	other threads:[~1995-08-21  3:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-08-21  3:25 jmk [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-08-21 21:28 Brian
1995-08-21 12:20 Dirk
1995-08-21  5:04 Vadim
1995-08-21  3:26 jmk
1995-08-20 19:10 Dirk
1995-08-20 14:24 Scott
1995-08-20  4:09 jmk

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=19950821032526.SWZ-VjxubR1Cke8zDGxfmTTOUEXFRj_wMroHP0Bkycw@z \
    --to=jmk@plan9.att.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;
as well as URLs for NNTP newsgroup(s).