From: "Faccini, Bruno" <bruno.faccini@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Last "kernel update (relative to 2.4.0-test9)" patch/diff file
Date: Tue, 31 Oct 2000 14:22:48 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205643@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
David,
It seems to me that the latest patch/diff file you reported (as "kernel
update (relative to 2.4.0-test9)" in your email dated "Tue, 31 Oct 2000
00:55:03") to be available under
"ftp://ftp.kernel.org/pub/linux/kernel/ports/ia64/" has been installed with
the same/old "linux-2_4_0-test9-ia64-001004_diff.[gz,bz2]" name, and
overidded the older file version (only the file time-stamp attest of the
update/new version).
Its content is ok (ie "linux-001030.diff") at least for its time-stamp'ed
name. But newer ("linux-001030.diff") is half size (1219Kb vs 2028Kb) of the
older ("linux-2.4.0-test9-ia64-001004.diff") !!
All of this is a little bit confusing.
So what is the exact process to apply this last patch, just a next diff to
be applied on-top/in-addition of the Base "-test9" tar-ball + the old
patch, or is it a full replacement patch for the old one to be again applied
on a virgin Base "-test9" Kernel source tree ??
Thank's.
Bruno.
> Bruno Faccini - Tech. Mktg. Engr.
> Technical Marketing/Internet Solutions Group (EMEA)
> Intel GmbH, Germany
> Phone (Intel office): +33-(0)146947228
> Fax: +33-(0)146947068
> email: bruno.faccini@intel.com
>
<<Bruno Faccini (E-mail).vcf>>
[-- Attachment #2: Bruno Faccini (E-mail).vcf --]
[-- Type: application/octet-stream, Size: 873 bytes --]
BEGIN:VCARD
VERSION:2.1
N:Faccini;Bruno;;;
FN:Bruno Faccini
ORG:Intel;Technical Marketing/Content Group EMEA
TITLE:Tech. Mktg. Engr.
TEL;WORK;VOICE:+33 (0) 146947228
TEL;WORK;VOICE:+33 (0) 155498427
TEL;HOME;VOICE:
TEL;CELL;VOICE:
TEL;WORK;FAX:+33 (0) 146947068
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;Munich, Germany.;Intel Corporation=0D=0ATour Chenonceaux=0D=0A204 Rond Poin=
t Du Pont De Sevres;Boulogne Billancourt;Cedex;92516;France
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Munich, Germany.=0D=0AIntel Corporation=0D=0ATour Chenonceaux=0D=0A204 Rond =
Point Du Pont De Sevres=0D=0ABoulogne Billancourt, Cedex 92516=0D=0AFrance
ADR;HOME:;;20 Rue Du Marechal Joffre;Brie Comte Robert;;77170;France
LABEL;HOME;ENCODING=QUOTED-PRINTABLE:20 Rue Du Marechal Joffre=0D=0ABrie Comte Robert 77170=0D=0AFrance
EMAIL;PREF;INTERNET:bruno.faccini@intel.com
REV:20000527T141533Z
END:VCARD
reply other threads:[~2000-10-31 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590678205643@msgid-missing \
--to=bruno.faccini@intel.com \
--cc=linux-ia64@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.