From: Jens Lehmann <Jens.Lehmann@web.de>
To: Cole <cole.minnaar@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH/RFC] submodule: add ability to shallowly clone any branch in a submodule
Date: Sat, 13 Sep 2014 13:21:54 +0200 [thread overview]
Message-ID: <541428D2.1080001@web.de> (raw)
In-Reply-To: <1410467134-sup-6791@Sasori.local>
Am 11.09.2014 um 22:33 schrieb Cole:
> Thanks for the feedback, really appreciate it, and will try to reformat
> the patches as you have asked.
Thanks!
> When you say you would like the patches split, do you mean into two
> separate threads, or just different patches part of the same thread?
I think you are solving a single problem here (submodule update does
not work with branch and depth), so I'd propose a single thread for
that topic.
> As for --no-single-branch on 'git submodule update', I didn't want to
> break existing functionality, but if you would prefer that to be the
> default I can make it so.
We should discuss if --no-single-branch should be implied when used
with a branch. I believe that if one option needs another one to work,
we should think about implying the latter. But might be wrong on that
with regards to --no-single-branch because I missed something obvious
... ;-)
> Also if there is anything else you are currently looking at regarding
> submodules or thinking about, I would be glad to hear about it or to try
> look at it while I am working on these changes. Or if there is anything
> you can think of for me to check with regards to these changes that
> would also be appreciated.
Sure, I keep a Todo list on the Wiki of my GitHub-repo:
https://github.com/jlehmann/git-submod-enhancements/wiki#issues-still-to-be-tackled
If you want to work on some of those - or other - topic(s), I'll be
happy to help.
> I am still quite new to some of the git terms and functionality,
> so please excuse me if I do get anything wrong or do not fully understand.
No worries, we're all still learning ;-)
prev parent reply other threads:[~2014-09-13 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 17:11 [PATCH/RFC] submodule: add ability to shallowly clone any branch in a submodule Cole Minnaar
2014-09-11 19:21 ` Jens Lehmann
2014-09-11 20:33 ` Cole
2014-09-12 5:21 ` Fredrik Gustafsson
2014-09-13 11:11 ` Jens Lehmann
2014-09-13 11:21 ` Jens Lehmann [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=541428D2.1080001@web.de \
--to=jens.lehmann@web.de \
--cc=cole.minnaar@gmail.com \
--cc=git@vger.kernel.org \
/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).