From: Yury Umanets <umka@namesys.com>
To: Andrew Clausen <clausen@gnu.org>
Cc: reiserfs-list@namesys.com
Subject: Re: aal_assert()
Date: Fri, 10 Jan 2003 17:12:30 +0300 [thread overview]
Message-ID: <3E1ED4CE.2010104@namesys.com> (raw)
In-Reply-To: <20030110133657.GE1056@gnu.org>
Andrew Clausen wrote:
>On Fri, Jan 10, 2003 at 10:22:43AM +0300, Yura Umanets wrote:
>
>
>>Actually there was the code earlier like you have proposed. And it was
>>changed to the current state due to the following reasons:
>>
>>* there are two developers working on reiser4progs currentry (Vitaly
>>Fertman and Yury Umanets). And our parts is much different. So, each of
>>us should work on own code.
>>* there is not neccessary an assertion is corect and only the author can
>>decide is it correct.
>>
>>
>
>Well, that decision is made by the developers, not the users.
>
Decision is made by developers in debug and test stage.
>Presumebly, you know who wrote what code. If an assertion is
>contentious (and 99.9% of them aren't), you should document *why*,
>anyway.
>
I should document why an assert is contentious? I think there should not
exist contentious assersions. Assertion is correct or not.
>
>
>
>>* NAMESYS has some development policies. And hints is the one of them.
>>
>>
>
>Why?
>
I don't know :)) Probably Nikita will tell you better. Hi is the old
resident of NAMESYS.
>
>Cheers,
>Andrew
>
>
>
>
>
--
Yury Umanets
next prev parent reply other threads:[~2003-01-10 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 0:54 aal_assert() Andrew Clausen
2003-01-10 7:22 ` aal_assert() Yury Umanets
2003-01-10 13:36 ` aal_assert() Andrew Clausen
2003-01-10 14:12 ` Yury Umanets [this message]
[not found] ` <15901.23872.24060.68353@laputa.namesys.com>
2003-01-10 13:26 ` aal_assert() Andrew Clausen
2003-01-10 13:19 ` aal_assert() Yury Umanets
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=3E1ED4CE.2010104@namesys.com \
--to=umka@namesys.com \
--cc=clausen@gnu.org \
--cc=reiserfs-list@namesys.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 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.