From: Ben Knoble <ben.knoble@gmail.com>
To: Jordan K <jordankadish93@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Branch Awareness
Date: Fri, 20 Nov 2026 21:38:55 -0500 [thread overview]
Message-ID: <71943758-1A3B-44F5-9BDA-233F16AC41C7@gmail.com> (raw)
In-Reply-To: <CAA8YNQAsyUe275DLPRnB4dym5aq9ZyemA39u+HJciKzat5tNQA@mail.gmail.com>
> Le 19 nov. 2026 à 04:54, Jordan K <jordankadish93@gmail.com> a écrit :
>
> I have a situation at my current workplace that led me to consider this feature:
>
> We crudely pass around a `settings.py` file that doesn't match the one
> stored in our `main` branch, as many workplaces do.
We sometimes carry « .env.example » that folks should modify
into « .env », which is ignored.
prev parent reply other threads:[~2026-11-21 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 9:54 Branch Awareness Jordan K
2026-11-19 12:27 ` 謝晉凡 Hsieh Chin Fan
2026-11-21 2:38 ` Ben Knoble [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=71943758-1A3B-44F5-9BDA-233F16AC41C7@gmail.com \
--to=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=jordankadish93@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox