Am 07.08.2013 20:28, schrieb Fredrik Gustafsson:
On Tue, Aug 06, 2013 at 02:11:56PM -0700, Junio C Hamano wrote:
Thanks, will replace the top two commits and queue. Looks like we
are getting ready for 'next'?
I'm a bit curious about if we should move towards a reentrent libgit
(which would
On Thu, Aug 08, 2013 at 07:11:04PM +0200, Jens Lehmann wrote:
Am 07.08.2013 20:28, schrieb Fredrik Gustafsson:
On Tue, Aug 06, 2013 at 02:11:56PM -0700, Junio C Hamano wrote:
Thanks, will replace the top two commits and queue. Looks like we
are getting ready for 'next'?
I'm a bit
Am 06.08.2013 23:11, schrieb Junio C Hamano:
Thanks, will replace the top two commits and queue. Looks like we
are getting ready for 'next'?
I hope so, I'm not aware of any open issues.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to
On Tue, Aug 06, 2013 at 02:11:56PM -0700, Junio C Hamano wrote:
Thanks, will replace the top two commits and queue. Looks like we
are getting ready for 'next'?
I'm a bit curious about if we should move towards a reentrent libgit
(which would for example make multithreading easier) or not.
If
Currently using git rm on a submodule removes the submodule's work tree
from that of the superproject and the gitlink from the index. But the
submodule's section in .gitmodules is left untouched, which is a leftover
of the now removed submodule and might irritate users (as opposed to the
setting
Thanks, will replace the top two commits and queue. Looks like we
are getting ready for 'next'?
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
6 matches
Mail list logo