From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: fixes
Date: Thu, 17 Aug 1995 21:02:22 -0400 [thread overview]
Message-ID: <19950818010222.sFj2pJqP5J_T9oQqV7GMj1XvBdKVhQAEIC1zve6NR1I@z> (raw)
>>if people are going to post source, please post diffs
>>as they highlight the fix rather than hiding it.
yes, and it is probably ill-advised to put too much of THE SOURCE
out in public, since it is subject to licence. diffs sometimes
beg the question of a reference source (if you haven't got the
CDROM on line), and they do not always avoid excessive detail, esp. without -b,
but seem a reasonable compromise. diff -e is quite
effective at hiding detail, but troublesome and downright confusing
if the reference source turns out to be wrong!
in Old Unix days there was some light-hearted discussion about whether
it would be possible to reconstruct THAT SOURCE by accumulating
all the diffs that had been published; enough people took
the possibility seriously enough to try to ensure that only
people with a licence could subscribe to the newsletters with the diffs.
during the discussion about comp.os.plan9, it struck me
that one of the advantages of a moderated newsgroup
was that a moderator might spot the more obvious violations.
even so, i don't mean to dent Vadim Antonov's enthusiasm, since it is
natural to want to share joys; or, in Bill Hogan's case, misery.
next reply other threads:[~1995-08-18 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-18 1:02 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-18 13:57 fixes Scott
1995-08-18 3:41 fixes dhog
1995-08-18 1:34 fixes Bruce
1995-08-17 11:32 fixes Vadim
1995-08-17 11:13 fixes Vadim
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=19950818010222.sFj2pJqP5J_T9oQqV7GMj1XvBdKVhQAEIC1zve6NR1I@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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).