9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] venti woes with brand new install
Date: Sun,  9 Sep 2007 15:08:38 +0200	[thread overview]
Message-ID: <5d375e920709090608l216ec4a7s55e81c700a0ad724@mail.gmail.com> (raw)
In-Reply-To: <46e3edc6.1c185e0a.1ae5.60da@mx.google.com>

Even if you know C, the reasons and purpose of a change are very often
non-obvious. Specially if you are not familiar with the code being
changed and all you want to know is if whatever bug was bothering you
is supposedly fixed or not (so you can test it and provide due
feedback).

uriel

On 9/9/07, John Soros <sorosj@gmail.com> wrote:
> True, but there are no comments at all, so I can't really know what the changes fix.
> I'm thinking, as i'm not a big C hacker, that a completely different change might be made to fix the problem, and the change i'm waiting for would then never appear.
> Oh well, I guess I'm expecting a lot: "comments", but at the same time, without those how should we know what's happening and why?
>
> oh well, i guess the answer to this would be "learn C", and btw that is what i'm doing.
>
> Regards
> John
>
>
> On Sun, 9 Sep 2007 08:05:06 -0400
> erik quanstrom <quanstro@quanstro.net> wrote:
>
> > you can use history(1) on sources.
> >
> > cpu% 9fs sources
> > cpu% cd /n/sources/plan9/sys/src/cmd/venti/srv
> > cpu% history ifile.c
> > Sep  8 23:03:56 EDT 2007 ifile.c 2592 [geoff]
> > Sep  8 23:03:56 EDT 2007 /n/sourcesdump/2007/0909/plan9/sys/src/cmd/venti/srv/ifile.c 2592 [geoff]
> > Apr 25 17:03:46 EDT 2007 /n/sourcesdump/2007/0908/plan9/sys/src/cmd/venti/srv/ifile.c 2327 [geoff]
> >
> > - erik
> >
> > > Hi, again me.
> > > I'm wondering how I will know when I can get back to using the sources venti, a changelog of
> > > some-sort would be welcomed to see when a specific change has been made. For example this time
> > > it would be nice to know when I need not be worried about being able to boot with venti if I
> > > recompile the kernel. Thanks for the help, the new kernel with modified venti still works fine.
> > > Cheers John
> >
>


  reply	other threads:[~2007-09-09 13:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-08 12:09 John Soros
2007-09-08 13:43 ` erik quanstrom
2007-09-08 14:27   ` gabidiaz
2007-09-09 12:01   ` John Soros
2007-09-09 12:05     ` erik quanstrom
2007-09-09 12:57       ` John Soros
2007-09-09 13:08         ` Uriel [this message]
2007-09-09 13:13         ` erik quanstrom
2007-09-09 13:22           ` Uriel
2007-09-10  8:12     ` SHRIZZA
2007-09-10  8:39       ` Uriel
2007-09-08 15:27 cinap_lenrek
2007-09-08 16:49 ` erik quanstrom
2007-09-08 17:07   ` cinap_lenrek
2007-09-08 19:08   ` cinap_lenrek
2007-09-08 21:45     ` John Soros

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=5d375e920709090608l216ec4a7s55e81c700a0ad724@mail.gmail.com \
    --to=uriel99@gmail.com \
    --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).