On Wed, Dec 11, 2013 at 03:16:24PM -0800, Junio C Hamano wrote:
Jens Lehmann jens.lehm...@web.de writes:
I think this is closely related to Martin's list of wishes we
earlier saw in the thread: remind the user to push necessary
submodule tip before the top-level commit that needs that
Am 10.12.2013 00:56, schrieb Junio C Hamano:
Heiko Voigt hvo...@hvoigt.net writes:
On Fri, Dec 06, 2013 at 02:40:15PM -0500, Martin Langhoff wrote:
On Fri, Dec 6, 2013 at 3:48 AM, Jens Lehmann jens.lehm...@web.de wrote:
Right you are, we need tutorials for the most prominent use cases.
In
Jens Lehmann jens.lehm...@web.de writes:
I think this is closely related to Martin's list of wishes we
earlier saw in the thread: remind the user to push necessary
submodule tip before the top-level commit that needs that commit in
the submodule is pushed out. Giving projects a way to
On Fri, Dec 06, 2013 at 02:40:15PM -0500, Martin Langhoff wrote:
On Fri, Dec 6, 2013 at 3:48 AM, Jens Lehmann jens.lehm...@web.de wrote:
Right you are, we need tutorials for the most prominent use cases.
In the meantime, are there any hints? Emails on this list showing a
current smart
Heiko Voigt hvo...@hvoigt.net writes:
On Fri, Dec 06, 2013 at 02:40:15PM -0500, Martin Langhoff wrote:
On Fri, Dec 6, 2013 at 3:48 AM, Jens Lehmann jens.lehm...@web.de wrote:
Right you are, we need tutorials for the most prominent use cases.
In the meantime, are there any hints? Emails on
Am 05.12.2013 23:06, schrieb Martin Langhoff:
On Thu, Dec 5, 2013 at 2:54 PM, Jens Lehmann jens.lehm...@web.de wrote:
Am 05.12.2013 20:27, schrieb Martin Langhoff:
On Thu, Dec 5, 2013 at 2:18 PM, Jens Lehmann jens.lehm...@web.de wrote:
Without knowing more I can't think of a reason why
On Fri, Dec 6, 2013 at 3:48 AM, Jens Lehmann jens.lehm...@web.de wrote:
Right you are, we need tutorials for the most prominent use cases.
In the meantime, are there any hints? Emails on this list showing a
current smart workflow? Blog posts? Notes on a wiki?
Early git was very pedantic, and
On Wed, Dec 4, 2013 at 6:01 PM, Martin Langhoff
martin.langh...@gmail.com wrote:
Is there a reasonable approach to scripting this?
Found my answers.
The 'subtree' merge strategy is smart enough to mostly help here.
However, it does not handle new files created in the subdirectory.
My workflow
Am 05.12.2013 00:01, schrieb Martin Langhoff:
Hi folks.
currently working on a project based on Moodle (the LMS that got me
into git in the first place). This is a highly modular software, and I
would like to maintain a bunch of out of tree modules in a single
repository, and be able to
On Thu, Dec 5, 2013 at 2:18 PM, Jens Lehmann jens.lehm...@web.de wrote:
Without knowing more I can't think of a reason why submodules should
not suit your use case (but you'd have to script branching and tagging
yourself until these commands learn to recurse into submodules too).
The
Am 05.12.2013 20:27, schrieb Martin Langhoff:
On Thu, Dec 5, 2013 at 2:18 PM, Jens Lehmann jens.lehm...@web.de wrote:
Without knowing more I can't think of a reason why submodules should
not suit your use case (but you'd have to script branching and tagging
yourself until these commands learn
On Thu, Dec 5, 2013 at 2:54 PM, Jens Lehmann jens.lehm...@web.de wrote:
Am 05.12.2013 20:27, schrieb Martin Langhoff:
On Thu, Dec 5, 2013 at 2:18 PM, Jens Lehmann jens.lehm...@web.de wrote:
Without knowing more I can't think of a reason why submodules should
not suit your use case (but you'd
Hi folks.
currently working on a project based on Moodle (the LMS that got me
into git in the first place). This is a highly modular software, and I
would like to maintain a bunch of out of tree modules in a single
repository, and be able to publish them in per-module repositories.
So I would
13 matches
Mail list logo
