From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: git@vger•kernel.org
Subject: Re: [Bug] branch.*.merge interpreted too strictly by tracking logic
Date: Wed, 05 Feb 2014 13:10:42 -0800 [thread overview]
Message-ID: <xmqq38jx2rl9.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140205210831.GB16753@sigill.intra.peff.net> (Jeff King's message of "Wed, 5 Feb 2014 16:08:31 -0500")
Jeff King <peff@peff•net> writes:
> .... Did your report come
> out of a real case, or was it just something you noticed?
Some git-wrappers (like "repo") are reported to muck with the
configuration files.
next prev parent reply other threads:[~2014-02-05 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 22:49 [Bug] branch.*.merge interpreted too strictly by tracking logic Junio C Hamano
2014-02-05 20:50 ` Jeff King
2014-02-05 21:05 ` Junio C Hamano
2014-02-05 21:08 ` Jeff King
2014-02-05 21:10 ` Junio C Hamano [this message]
2014-10-14 22:14 ` [PATCH] checkout: report upstream correctly even with loosely defined branch.*.merge Junio C Hamano
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=xmqq38jx2rl9.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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