Messages in this thread | | | From | Bernd Eckenfels <> | Subject | Re: [PATCH] linuxabi | Date | Wed, 01 Oct 2003 04:05:57 +0200 |
| |
In article <UTC200310010001.h9101NU17078.aeb@smtp.cwi.nl> you wrote: > +These headers are "append-only", in the sense that Linux > +tries to keep supporting old interfaces.
I dont think this is true. Neighter was is true in the past nor is it desireable in all cases. We may define a range of releases, where the ABI will be stable, but I am not sure we find a text everybody agrees on.
I do think it is not a bead idea to keep deprecated values at least commented out, to avoid reuse, whenever possible.
Otherwise I love the idea. Have you checked back with the Glibc folks?
> +#define MS_NODIRATIME 2048 /* Do not update directory access times */ > +#define MS_BIND 4096 > +#define MS_POSIXACL (1<<16) /* VFS does not apply the umask */
can we clean that up? with shifting, without shifting, with comments and without comments? I suggest to use the linuxdoc comments mandatory for the abi files.
> + * Old magic mount flag and mask
i also suggest to think twice about using the word old somewhere. valid-since, deprecated-after may be used in conjunction with version identifiers. And not including deprecated symbols is also a good start.
Greetings Bernd -- eckes privat - http://www.eckes.org/ Project Freefire - http://www.freefire.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |