bump. it's been a while and I'm still not clear what the next steps
are. I'm happy to send a patch but I would like to get a consensus
first.
On Wed, May 31, 2017 at 10:50 AM, John Shahid wrote:
> Hi Jonathan. Thanks a lot for the detailed and interesting response. I
>
On Mon, Jun 12, 2017 at 1:27 PM, Stefan Beller wrote:
> On Sat, Jun 10, 2017 at 6:28 AM, John Shahid wrote:
>> bump. it's been a while and I'm still not clear what the next steps
>> are. I'm happy to send a patch but I would like to get a consensus
>> first.
Hi all,
It looks like the git push recurse-submodules behavior has changed.
Currently with 2.13 you cannot run "git push
--recurse-submodules=on-demand" if the parent repo is on a different
branch than the sub repos, e.g. parent repo is on "develop" and
sub-repo on "master". I created a test that
al path) to not propagate the
refspec and preserve the current behavior. Judging from the code and a
test case that I wrote, this behavior is working as expected. That is,
git won't propagate the refspec.
Cheers,
JS
On Mon, May 29, 2017 at 12:20 AM, Stefan Beller wrote:
> On Sun, May 28, 20
corrected
3. I propose more changes to the git tools to support the unity view of the repo
On Tue, May 30, 2017 at 2:10 PM, Jonathan Nieder wrote:
> Hi John,
>
> John Shahid wrote:
>
>> It looks like the git push recurse-submodules behavior has changed.
>> Currently with 2.13
5 matches
Mail list logo
