From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Dave Jones <davej@suse.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
bjornw@axis.com
Subject: Re: cris patches in 2.5.3-pre3.
Date: Tue, 22 Jan 2002 10:26:32 -0500 [thread overview]
Message-ID: <3C4D84A8.A404CCFC@mandrakesoft.com> (raw)
In-Reply-To: <20020122151951.A16157@suse.de>
Dave Jones wrote:
> Some of the cris patches in pre3 seem to be going backwards.
> Is this intentional? Or just CVS weirdness ?
> -# $Id: Makefile,v 1.22 2001/10/01 14:42:38 bjornw Exp $
> +# $Id: Makefile,v 1.3 2002/01/21 15:21:23 bjornw Exp $
from 2001 -> 2002
> -/* $Id: head.S,v 1.8 2001/10/03 17:15:15 bjornw Exp $
> +/* $Id: head.S,v 1.2 2001/12/18 13:35:12 bjornw Exp $
from october -> december
looks ok to me, do I need more caffeine? :)
Jeff
--
Jeff Garzik | "I went through my candy like hot oatmeal
Building 1024 | through an internally-buttered weasel."
MandrakeSoft | - goats.com
next prev parent reply other threads:[~2002-01-22 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 15:19 cris patches in 2.5.3-pre3 Dave Jones
2002-01-22 15:26 ` Jeff Garzik [this message]
2002-01-22 15:32 ` Dave Jones
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=3C4D84A8.A404CCFC@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=bjornw@axis.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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