From: Stefan Beller <sbeller@google.com>
To: Sebastian Schuberth <sschuberth@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Jens Lehmann <Jens.Lehmann@web.de>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH 3/5] submodule-config: keep labels around
Date: Mon, 25 Jan 2016 10:06:31 -0800 [thread overview]
Message-ID: <CAGZ79kZAt1wfqrf1Hk2p5tx=m9OXednsyRFYP6VeVcG69Do91g@mail.gmail.com> (raw)
In-Reply-To: <CAHGBnuMM5KWMUZd_ZNkEvP_homqy4kg3z356V3fhsLveZhjtBA@mail.gmail.com>
On Sun, Jan 24, 2016 at 10:06 AM, Sebastian Schuberth
<sschuberth@gmail.com> wrote:
> On Sat, Jan 23, 2016 at 1:31 AM, Stefan Beller <sbeller@google.com> wrote:
>
>> We need the submodule groups in a later patch.
>
> The commit message should now say "labels", too, I guess.
Sure, thanks for catching!
>
> --
> Sebastian Schuberth
next prev parent reply other threads:[~2016-01-25 18:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 0:31 [RFC/PATCH 0/5] [WAS: Submodule Groups] Labels and submodule.autoInitialize Stefan Beller
2016-01-23 0:31 ` [PATCH 1/5] submodule init: Write submodule registration to stderr Stefan Beller
2016-01-23 0:31 ` [PATCH 2/5] git submodule: Teach add to label submodules Stefan Beller
2016-01-23 0:31 ` [PATCH 3/5] submodule-config: keep labels around Stefan Beller
2016-01-24 18:06 ` Sebastian Schuberth
2016-01-25 18:06 ` Stefan Beller [this message]
2016-01-23 0:31 ` [PATCH 4/5] submodule update: respect submodule.autoInitialize Stefan Beller
2016-01-23 0:31 ` [PATCH 5/5] builtin/clone: Configure submodule.autoInitialize via --init-submodule Stefan Beller
2016-01-24 19:38 ` [RFC/PATCH 0/5] [WAS: Submodule Groups] Labels and submodule.autoInitialize Jens Lehmann
2016-01-25 18:59 ` Stefan Beller
2016-01-26 20:59 ` Jens Lehmann
2016-01-26 21:50 ` Stefan Beller
2016-01-31 21:09 ` Jens Lehmann
2016-02-01 20:21 ` Stefan Beller
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGZ79kZAt1wfqrf1Hk2p5tx=m9OXednsyRFYP6VeVcG69Do91g@mail.gmail.com' \
--to=sbeller@google.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=sschuberth@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).