From: Martin Langhoff <martin.langhoff@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: git "thin" submodule clone to feed "describe"
Date: Tue, 23 Feb 2016 20:28:42 -0500 [thread overview]
Message-ID: <CACPiFCJ216dx9s6YynH2d8StyNxR4zci9OhGKH4BbJXXf4SSUA@mail.gmail.com> (raw)
In-Reply-To: <xmqq1t83yuv6.fsf@gitster.mtv.corp.google.com>
On Tue, Feb 23, 2016 at 4:33 PM, Junio C Hamano <gitster@pobox.com> wrote:
> No, I do not think so.
Thanks. I will probably setup a pre-commit hook at the top level
project to update a submodule metadata file.
Not the prettiest but... :-)
m
--
martin.langhoff@gmail.com
- ask interesting questions
- don't get distracted with shiny stuff - working code first
~ http://docs.moodle.org/en/User:Martin_Langhoff
prev parent reply other threads:[~2016-02-24 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 21:03 git "thin" submodule clone to feed "describe" Martin Langhoff
2016-02-23 21:33 ` Junio C Hamano
2016-02-24 1:28 ` Martin Langhoff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACPiFCJ216dx9s6YynH2d8StyNxR4zci9OhGKH4BbJXXf4SSUA@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).