From: Junio C Hamano <gitster@pobox•com>
To: Brooke Kuhlmann <brooke@alchemists•io>
Cc: Taylor Blau <me@ttaylorr•com>, git@vger•kernel.org
Subject: Re: Git Commit Notes (fetching/pushing)
Date: Sun, 06 Aug 2023 18:07:30 -0700 [thread overview]
Message-ID: <xmqqwmy7irsd.fsf@gitster.g> (raw)
In-Reply-To: <3A1AEE32-4A0C-445D-A1D8-146CDCA03563@alchemists.io> (Brooke Kuhlmann's message of "Sun, 6 Aug 2023 15:49:22 -0600")
Brooke Kuhlmann <brooke@alchemists•io> writes:
> ... o why default branch push behavior is being
> ignored/overwritten.
The root of your confusion lies around here, I think. The "default"
branch push behaviour is given only when you do not customize. Once
you add customization, you would specify _exactly_ what you want.
In other words, the customization is NOT something you tell Git to
do _in addition to_ what it does anyway (otherwise you would not be
able to configure _away_ what is usually done by default when you do
not want to see it done).
next prev parent reply other threads:[~2023-08-07 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 18:35 Git Commit Notes (fetching/pushing) Brooke Kuhlmann
2023-08-06 20:09 ` Taylor Blau
2023-08-06 21:49 ` Brooke Kuhlmann
2023-08-07 1:07 ` Junio C Hamano [this message]
2023-08-07 14:02 ` Brooke Kuhlmann
2023-08-07 16:14 ` Junio C Hamano
2023-08-07 20:18 ` Brooke Kuhlmann
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=xmqqwmy7irsd.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=brooke@alchemists$(echo .)io \
--cc=git@vger$(echo .)kernel.org \
--cc=me@ttaylorr$(echo .)com \
/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