>> >http://www.netbsd.org/Releases/release-map.html
>> 
>> that still doesn't answer the question of which is a subset of which.
>> i always assumed that the release branch was a proper subset of the
>> current branch (assuming of course that you don't want to try to mail
>> jelly to a tree and call it a trunk).
>
>Take a look at the diagram.  1.4 is a separate branch from
>-current.  Essentially, when 1.4 is released, two separate branches are
>created.  Bug fixes, perhaps some drivers, etc... are pulled from -current
>into the 1.4 branch from time to time, but they are separate
>branches.  When sufficient bug fixes or little features are added to 1.4,
>it becomes 1.4.1 (then 1.4.2).  At that point, -current may be completely
>different due to structure or archtecture changes.  So it would be proper
>to say that the 1.4 branch contains all of -current _at the time the
>source was branched_.  Past that, -current and 1.4 diverge; -current
>remains the ever growing trunk of the tree, while 1.4 grows for a while,
>then ends.

certainly, in terms of the engineering of the tree itself (names
change, things move, things get better, certain vestigial features are
trimmed), but i'm speaking in slightly more gross terms.

i always believed that, as far as support for devices goes, the
current "trunk" (from which all releases are grown) contains support
for all the stuff that any release ever contained, whereas current has
support in it for things that no release (yet) has supported.  that,
to me at least, makes current a proper superset of the release, or
conversely, the release a proper subset of the "trunk".  no?

>Ne pas?

je ne sais pas.  :(

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."