Re: [PATCH] Fix bad data from non-direct-io read after direct-io write

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Zach Brown <zach.brown@...>
Cc: Karl Schendel <kschendel@...>, Benjamin LaHaise <bcrl@...>, Andrew Morton <akpm@...>, Linux Kernel Mailing List <linux-kernel@...>, Nick Piggin <nickpiggin@...>, Chris Mason <chris.mason@...>
Date: Tuesday, October 30, 2007 - 3:11 pm

On Tue, 30 Oct 2007, Zach Brown wrote:

Thanks, will apply.


If it's one of these "in a blue moon" things I don't think it matters. 
Whatever is easier. 

In general, patches have lots of advantages: (a) you can apply it 
regardless of version, and (b) pushing the email containing them back and 
forth with commentary etc is very powerful.

So I would generally see git as a "maintainer handling issue", not a 
"these kinds of fixes" issue. Git doesn't obviate the need for having 
people look at patches (and that implies sending them out). But git _is_ a 
good way to push the finished product out, if it's a recurring thing.

		Linus
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH] Fix bad data from non-direct-io read after direc..., Linus Torvalds, (Tue Oct 30, 3:11 pm)