Skip to contentSkip to conversation

Why no linux-2.6.8.2? (was Re: new dev model)

DISCUSSION Chuck Ebbert 5 participants 6 messages Oct 7, 2004 – Dec 31, 2004

lore
Share & tools
lore
#0 lore raw

Why has linux 2.6.8 been abandoned at version 2.6.8.1?

There exist fixes that could go into 2.6.8.2:

process start time doesn't match system time FDDI frame doesn't allow 802.3 hwtype
NFS server using XFS filesystem on SMP machine oopses

I'm sure there are more...

So why is 2.6.8.1 a "dead branch?"

--Chuck Ebbert

#1 lore raw

Hi Chuck,

We don't usually make a 4th point in our versions, the next version after 2.6.8 would usually be 2.6.9, which will come out in due course.

2.6.8.1 was released because there was a 1-line error in 2.6.8 that completely stopped NFS from working.

The patches mentioned below will probably go into 2.6.9 or something, if they have been approved for it etc.

Hope that clears it up.

Cheers,
Trent
Bur.st

Quoted 21 lines

Why has linux 2.6.8 been abandoned at version 2.6.8.1?

There exist fixes that could go into 2.6.8.2:

process start time doesn't match system time FDDI frame doesn't allow 802.3 hwtype
NFS server using XFS filesystem on SMP machine oopses

I'm sure there are more...

So why is 2.6.8.1 a "dead branch?"

--Chuck Ebbert

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 2 lines
Trent Lloyd <[email protected]>
Bur.st Networking Inc.
#2 lore raw
In reply to Chuck Ebbert
Quoted 11 lines · Chuck Ebbert

Why has linux 2.6.8 been abandoned at version 2.6.8.1?

There exist fixes that could go into 2.6.8.2:

process start time doesn't match system time FDDI frame doesn't allow 802.3 hwtype
NFS server using XFS filesystem on SMP machine oopses

I'm sure there are more...

So why is 2.6.8.1 a "dead branch?"

It was an emergency "paperbag" release number.

All paperbag releases are made from dead branches.

#3 lore raw
Quoted 10 lines · alan
Quoted 8 lines · Chuck Ebbert

Why has linux 2.6.8 been abandoned at version 2.6.8.1?

There exist fixes that could go into 2.6.8.2:

process start time doesn't match system time FDDI frame doesn't allow 802.3 hwtype
NFS server using XFS filesystem on SMP machine oopses

Quoted 7 lines
Quoted 3 lines

I'm sure there are more...

So why is 2.6.8.1 a "dead branch?"

It was an emergency "paperbag" release number.

All paperbag releases are made from dead branches.

Thanks to BitKeeper no properly-tagged branch is ever dead.

Anyone could make a 2.6.8.2 if they so chose.

Jeff

#4 lore raw
In reply to Chuck Ebbert
Quoted 11 lines · Chuck Ebbert

Why has linux 2.6.8 been abandoned at version 2.6.8.1?

There exist fixes that could go into 2.6.8.2:

process start time doesn't match system time FDDI frame doesn't allow 802.3 hwtype
NFS server using XFS filesystem on SMP machine oopses

I'm sure there are more...

So why is 2.6.8.1 a "dead branch?"

Since it's in BitKeeper, it's not dead, it's just sleeping...

$ bk clone -ql -rv2.6.8.1 linux-2.6 linux-2.6.8-branch
$ cpcset <cset> linux-2.6 linux-2.6.8-branch
$ # repeat for each <cset> to apply
$ cd linux-2.6.8-branch
$ bk vi Makefile	# bump version
$ bk tag v2.6.8.2
$ # release 2.6.8.2 ...
#5 lore raw
In reply to Chuck Ebbert
Quoted 7 lines · Chuck Ebbert

Why has linux 2.6.8 been abandoned at version 2.6.8.1?

There exist fixes that could go into 2.6.8.2:

process start time doesn't match system time FDDI frame doesn't allow 802.3 hwtype
NFS server using XFS filesystem on SMP machine oopses

- Qdisc alignment errors, effectivly killing almost every single Linux router.
- giant memory leaks when writing audio cds (IIRC)

Signature · 2 lines
Tomasz Torcz                "Funeral in the morning, IDE hacking
[email protected]    in the afternoon and evening." - Alan Cox