| To: | <linux-mips@linux-mips.org> |
|---|---|
| Subject: | Version control question. |
| From: | "Kaz Kylheku" <kaz@zeugmasystems.com> |
| Date: | Fri, 11 Aug 2006 14:31:49 -0700 |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| Sender: | linux-mips-bounce@linux-mips.org |
| Thread-index: | Aca9jY3DFRSZI5xHRa+mXFr/W9Ne2A== |
| Thread-topic: | Version control question. |
Is there any document that makes the linux-mips configuration management structure more obvious? I see that the 2.6.16 and 2.6.17 lines are in fact parallel branches, so that 2.6.16.27 is newer than 2.6.17. If something is broken in 2.6.17 but isn't in 2.6.16.27, what's the best way to find it? Just compare 2.6.16.27 to the closest parallel 2.6.17.x to see what the differences are? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Added MIPS RM9K watchdog driver, Dave Jones |
|---|---|
| Next by Date: | Re: Version control question., Ralf Baechle |
| Previous by Thread: | [PATCH] RM9000 serial driver, Thomas Koeller |
| Next by Thread: | Re: Version control question., Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |