Hi Michael:
Good Morning. :)
I see mh/lockfile and mh/lockfile-stdio were ​graduated to "master".
So. does this patch continue?
On top of mh/lockfile-stdio?
Thank you. ^_^
Yue Lin Ho
--
View this message in context:
http://git.661346.n2.nabble.com/What-s-cooking-in-git-git-Aug-2014-02-Fri-8
Hi Duy, Michael, Junio C Hamano:
Thanks for working on lock file issue.
Thank you! Thank you~
^_^
Yue Lin Ho
--
View this message in context:
http://git.661346.n2.nabble.com/What-s-cooking-in-git-git-Aug-2014-02-Fri-8-tp7616651p7618314.html
Sent from the git mailing list archive at Nabble.
On Sat, Sep 6, 2014 at 5:31 PM, Michael Haggerty wrote:
> So I've shamelessly labeled this "v4" of his patch series and I've
> left Duy as the author, because his commit message (which I used
> directly) has far more intellectual content than the code change. Duy,
> if that's not OK with you, plea
This patch applies on top of the patch series that I just sent [1]:
Lockfile correctness and refactoring, v4
It has the same effect as Duy's [2]
Keep .lock file paths absolute, v3
except that my patch series obviates the need for his patches 1/3 and
2/3. So only one patch remains, the e
4 matches
Mail list logo