On Jan 22, 2008 10:05 AM, <ab_lists@mac.com> wrote:You can use both: patches to distribute proposed changes, bundles to distribute the integrated (and presumably controlled) branches after changes are accepted. Of course, you can use a bundle to distribute a proposed change as well (as a topic branch), you have to decide for yourselves what works best. Patches are great for distributed review over a mailing list, but if only a couple of you and no mailing list that advantage diminishes. Mark - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Linus Torvalds | Linux 2.6.21-rc1 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| pageexec | Re: [stable] Linux 2.6.25.10 |
| Linus Torvalds | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Jarek Poplawski | [PATCH take 2] pkt_sched: Protect gen estimators under est_lock. |
git: | |
