Am 03.07.2013 01:26, schrieb Chris Packham:
On Wed, Jul 3, 2013 at 4:56 AM, Jens Lehmann jens.lehm...@web.de wrote:
Am 02.07.2013 12:12, schrieb Chris Packham:
--- a/Documentation/git-submodule.txt
+++ b/Documentation/git-submodule.txt
@@ -159,7 +159,9 @@ update::
This will make the
On 03/07/13 18:55, Jens Lehmann wrote:
Am 03.07.2013 01:26, schrieb Chris Packham:
On Wed, Jul 3, 2013 at 4:56 AM, Jens Lehmann jens.lehm...@web.de wrote:
Am 02.07.2013 12:12, schrieb Chris Packham:
--- a/Documentation/git-submodule.txt
+++ b/Documentation/git-submodule.txt
@@ -159,7 +159,9
On 03/07/13 19:54, Chris Packham wrote:
On a related note should I be updating Documentation/config.txt as well?
Even if it's a statement that this feature exists refer to
git-submodule(1) for details.
Answering my own question. While 'update' is mentioned it's possible
values are not.
--
Chris Packham judge.pack...@gmail.com writes:
On 03/07/13 19:54, Chris Packham wrote:
On a related note should I be updating Documentation/config.txt as well?
Even if it's a statement that this feature exists refer to
git-submodule(1) for details.
Answering my own question. While 'update'
Am 02.07.2013 12:12, schrieb Chris Packham:
Users can set submodule.$name.update to '!command' which will cause
'command' to be run instead of checkout/merge/rebase. This allows the
user some finer grained control over how the update is done. The primary
motivation for this was
On Wed, Jul 3, 2013 at 4:56 AM, Jens Lehmann jens.lehm...@web.de wrote:
Am 02.07.2013 12:12, schrieb Chris Packham:
--- a/Documentation/git-submodule.txt
+++ b/Documentation/git-submodule.txt
@@ -159,7 +159,9 @@ update::
This will make the submodules HEAD be detached unless `--rebase`
6 matches
Mail list logo