From: Vadim Antonov avg@postman.ncube.com
Subject: format for source diffs
Date: Mon, 21 Aug 1995 01:04:00 -0400 [thread overview]
Message-ID: <19950821050400.FBwzjnPVYFqLVSFoadgtSGVrokRtqynNL9ycYKZepR0@z> (raw)
From: Scott Schwartz <schwartz@galapagos.cse.psu.edu>
>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.
Aw! The next thing to port will be EMACS :)
An illustration to my point on functional completeness.
--vadim
next reply other threads:[~1995-08-21 5:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-21 5:04 Vadim [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 3:26 jmk
1995-08-21 3:25 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=19950821050400.FBwzjnPVYFqLVSFoadgtSGVrokRtqynNL9ycYKZepR0@z \
--to=9fans@9fans.net \
/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).