From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] better than what
Date: Mon, 15 Mar 2004 12:14:34 +0100 [thread overview]
Message-ID: <999207f32f95a89b0657cef49bf3ce83@plan9.escet.urjc.es> (raw)
In-Reply-To: <200403151000.i2FA00Lu072772@adat.davidashen.net>
[-- Attachment #1: Type: text/plain, Size: 193 bytes --]
I wouldn't call /n/sources/nemo improvements,
but anyway, I try to keep then up to date.
I merge often our changes with those in sources, and
push changed /n/sources/nemo files back again.
[-- Attachment #2: Type: message/rfc822, Size: 2530 bytes --]
From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: [9fans] better than what
Date: Mon, 15 Mar 2004 14:00:00 +0400 (AMT)
Message-ID: <200403151000.i2FA00Lu072772@adat.davidashen.net>
Various improved sources (/n/sources/nemo, for example), such as
alternative keyboard drivers and other things, are distributed as
replacements for files in the source tree. It is never known whether
they can safely replace files in the current source base or they
had been branched off a while ago and just writing them over would
lead to conflicts.
Any chance the improvements can be delivered in a form (e.g.
patch(1)), or context diff, or with a copy of the original tree,
or with another reference to the exact versions/dates of the original
files) that lets people like me know better than what the proposed
improvements are?
David
next prev parent reply other threads:[~2004-03-15 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 10:00 David Tolpin
2004-03-15 11:14 ` Fco.J.Ballesteros [this message]
2004-03-15 11:51 ` David Tolpin
2004-03-15 11:58 ` Fco.J.Ballesteros
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=999207f32f95a89b0657cef49bf3ce83@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
/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).