Patch workflow and git branches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Greg:

In your USB repository you keep two main branches: usb-linus and
usb-next.  As I understand it, patches that contain new development get
added to usb-next (which doesn't get pushed to Linus until the next
merge window), whereas patches fixing bugs in the upcoming release get
added to usb-linus (which gets pushed to Linus every week or so).

Doesn't it make more sense to add bug-fix patches to both branches?  
Not doing this increases the likelihood of conflicts, because new
development could well need to touch code that just had some sort of
fix applied.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux