Am 27.10.2010 um 07:04 schrieb Vincent van Ravesteijn:
Hi All,
I converted the two files about Rules and Recommendation into a LyX
document. You might want to have a look at it, and put your two cents
in there about coding principle, style and so forth. It is still a bit
a mess, but I hope
Stephan Witt wrote:
Maybe we can create another document on the design principles and
major structure in the LyX code. There are already some pieces, but we
have to get them up to date and to put them in one place.
Comments ?
perhaps kill the old ascii file (or move it to attic) so
perhaps kill the old ascii file (or move it to attic) so there is unambiguous
location.
Yes, I will. I wanted to wait until this new document is somewhat
decent (I'm not sure why though).
also you nice log about casts could be saved somewhere.
It's already in there, but I hide it in the
Vincent van Ravesteijn wrote:
I'm not yet sure whether we should make one document of both the
Rules/Language Advice/Style and the implementation/design issues.
i would prefer one doc.
pavel
Am 27.10.2010 um 07:04 schrieb Vincent van Ravesteijn:
> Hi All,
>
> I converted the two files about Rules and Recommendation into a LyX
> document. You might want to have a look at it, and put your two cents
> in there about coding principle, style and so forth. It is still a bit
> a mess, but
Stephan Witt wrote:
> > Maybe we can create another document on the design principles and
> > major structure in the LyX code. There are already some pieces, but we
> > have to get them up to date and to put them in one place.
> >
> > Comments ?
perhaps kill the old ascii file (or move it to
> perhaps kill the old ascii file (or move it to attic) so there is unambiguous
> location.
Yes, I will. I wanted to wait until this new document is somewhat
decent (I'm not sure why though).
>also you nice log about casts could be saved somewhere.
It's already in there, but I hide it in the
Vincent van Ravesteijn wrote:
> I'm not yet sure whether we should make one document of both the
> Rules/Language Advice/Style and the implementation/design issues.
i would prefer one doc.
pavel
Hi All,
I converted the two files about Rules and Recommendation into a LyX
document. You might want to have a look at it, and put your two cents
in there about coding principle, style and so forth. It is still a bit
a mess, but I hope it will get better.
Everyone is invited to edit. Please turn
Hi All,
I converted the two files about Rules and Recommendation into a LyX
document. You might want to have a look at it, and put your two cents
in there about coding principle, style and so forth. It is still a bit
a mess, but I hope it will get better.
Everyone is invited to edit. Please turn
Should be uncontroversial, but I'll wait for a nod.
I have a few more controversial ones up my sleeve...
Andre'
Index: Rules
===
--- Rules (revision 20603)
+++ Rules (working copy)
@@ -12,6 +12,7 @@
but still, we don't
Andre Poenitz [EMAIL PROTECTED] writes:
-We also require you to provide a ChangeLog entry with every patch, this
-describes shortly what the patch is doing. The ChangeLog entry follows
-this syntax:
+We also require you to provide a commit message entry with every patch,
+this describes
On Sun, Sep 30, 2007 at 05:42:51PM +0200, Jean-Marc Lasgouttes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
-We also require you to provide a ChangeLog entry with every patch, this
-describes shortly what the patch is doing. The ChangeLog entry follows
-this syntax:
+We also require
Andre Poenitz [EMAIL PROTECTED] writes:
So reformulate short?
Thanks.
JMarc
Should be uncontroversial, but I'll wait for a nod.
I have a few more controversial ones up my sleeve...
Andre'
Index: Rules
===
--- Rules (revision 20603)
+++ Rules (working copy)
@@ -12,6 +12,7 @@
but still, we don't
Andre Poenitz <[EMAIL PROTECTED]> writes:
> -We also require you to provide a ChangeLog entry with every patch, this
> -describes shortly what the patch is doing. The ChangeLog entry follows
> -this syntax:
> +We also require you to provide a commit message entry with every patch,
> +this
On Sun, Sep 30, 2007 at 05:42:51PM +0200, Jean-Marc Lasgouttes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> > -We also require you to provide a ChangeLog entry with every patch, this
> > -describes shortly what the patch is doing. The ChangeLog entry follows
> > -this syntax:
> > +We
Andre Poenitz <[EMAIL PROTECTED]> writes:
> So reformulate "short"?
Thanks.
JMarc
I'd like to use development/Code_rules in some modified version for
internal (more or less educational) purposes. I would of course include a
small header concerning the origin of the document.
Does anybody feel that this is not a good thing do?
Andre'
--
It'll take a long time to eat
On 07-Mar-2000 Andre Poenitz wrote:
I'd like to use development/Code_rules in some modified version for
internal (more or less educational) purposes. I would of course include a
small header concerning the origin of the document.
Does anybody feel that this is not a good thing do?
I
Andre Poenitz [EMAIL PROTECTED] writes:
| I'd like to use development/Code_rules in some modified version for
| internal (more or less educational) purposes. I would of course include a
| small header concerning the origin of the document.
|
| Does anybody feel that this is not a good thing
I'd like to use development/Code_rules in some modified version for
internal (more or less educational) purposes. I would of course include a
small header concerning the origin of the document.
Does anybody feel that this is not a good thing do?
Andre'
--
It'll take a long time to eat
On 07-Mar-2000 Andre Poenitz wrote:
>
> I'd like to use development/Code_rules in some modified version for
> internal (more or less educational) purposes. I would of course include a
> small header concerning the origin of the document.
>
> Does anybody feel that this is not a good thing
Andre Poenitz <[EMAIL PROTECTED]> writes:
| I'd like to use development/Code_rules in some modified version for
| internal (more or less educational) purposes. I would of course include a
| small header concerning the origin of the document.
|
| Does anybody feel that this is not a good thing
24 matches
Mail list logo
