All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Kalogirou <harkal@gmx.net>
To: Riley Williams <rhw@InfraDead.Org>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: ELKS not runnable.... (once again)
Date: 17 May 2002 22:28:26 +0300	[thread overview]
Message-ID: <1021663705.21866.9.camel@cool> (raw)
In-Reply-To: <Pine.LNX.4.21.0205171846270.12716-100000@Consulate.UFP.CX>

Την Παρ, 17-05-2002 στις 20:59, ο/η Riley Williams έγραψε:
> Hi Harry.
> 
> >> I don't understand it either. All I can be sure of is that the
> >> version produced by `cvs get -r elks-0_1_0 elks` has exactly the
> >> same problem, but the one produced by `cvs get -D 'Apr 30 12:00:00
> >> 2002' elks` does not, so the problem lies somewhere between those
> >> two versions.
> 
> > Why should we compare 0.1.0 with an older one?
> 
> We're not - we're comparing the official 0.1.0 release (which is the
> version timestamped as above) with the tagged 0.1.0 release (which is
> the one tagged elks-0_1_0 in the CVS tree) and finding they differ.
> 
> My comment above is pointing out that the version tagged as elks-0_1_0
> in the CVS tree is NOT the version that was released as 0.1.0 but a
> later version with some extra tweaks applied.

If the tag elks-0_1_0 has the timestamp you say and you checkout that
timestamp and there are differences then CVS has some BUG, which I don't
think so.

> 
> Which 0.1.0 release? As stated above, there are TWO DIFFERENT releases
> labelled as 0.1.0 depending on where one looks.
>

I checked it out with the tag elks-0_1_0. 
 
> > 3) The changes in the minix FS are very dangerous and require care. 
> 
> Agreed. That's why I'm carefully reverting them.
> 

That is good to hear...

Harry



-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2002-05-17 19:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 17:31 ELKS not runnable.... (once again) Harry Kalogirou
2002-05-15 18:46 ` pauln
2002-05-15 19:30   ` Harry Kalogirou
2002-05-17 20:15     ` ELKS not runnable.... (other thing) Stefan de Konink
2002-05-17 19:40       ` Harry Kalogirou
2002-05-15 21:25 ` ELKS not runnable.... (once again) Riley Williams
2002-05-15 23:11 ` Riley Williams
2002-05-16  9:40   ` Riley Williams
2002-05-16 21:53     ` Harry Kalogirou
2002-05-16 22:42       ` Riley Williams
2002-05-16 22:47         ` Dan Olson
2002-05-17 14:10         ` Harry Kalogirou
2002-05-17 17:59           ` Riley Williams
2002-05-17 19:28             ` Harry Kalogirou [this message]
2002-05-16  9:52   ` Harry Kalogirou

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=1021663705.21866.9.camel@cool \
    --to=harkal@gmx.net \
    --cc=linux-8086@vger.kernel.org \
    --cc=rhw@InfraDead.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.