From: Mihails Strasuns <mihails.strasuns@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Raphael Stolt <raphael.stolt@gmail.com>
Subject: Re: Is it possible to use new conditional includes outside of git dir?
Date: Thu, 18 May 2017 13:50:17 +0200 [thread overview]
Message-ID: <4a8c79b3-91e4-6f6c-23c3-74df023ffdf0@gmail.com> (raw)
In-Reply-To: <CACBZZX5z_jn3KnpgOBE=qa1cUcUAABPwuzqG81Ry0ztvMm4nAw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 901 bytes --]
On 05/15/2017 11:00 PM, Ævar Arnfjörð Bjarmason wrote:
> It's intentional, but in the "that's how this works" sense, not "we'll
> never add what you just asked for".
>
> This came up on list last week:
> https://public-inbox.org/git/F55DC360-9C1E-45B9-B8BA-39E1001BD620@gmail.com/T/#u
>
> So I'd like to ask you the same question I asked Raphael in that thread.
This came from the GitHub CLI tool I use
(https://github.com/sociomantic-tsunami/git-hub) which stores own
configuration in git config (i.e. `git config hub.oauthtoken`). Some of
its command run outside of the repository context, for example `git hub
clone` ensures creation of a personal fork before doing regular clone
and thus needs access to the token.
Thus I hoped that I will be able to use new git functionality to
distinguish between work and personal GitHub accounts same as it is done
for name/email.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 525 bytes --]
prev parent reply other threads:[~2017-05-18 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 18:09 Is it possible to use new conditional includes outside of git dir? Mihails Strasuns
2017-05-15 21:00 ` Ævar Arnfjörð Bjarmason
2017-05-18 11:50 ` Mihails Strasuns [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=4a8c79b3-91e4-6f6c-23c3-74df023ffdf0@gmail.com \
--to=mihails.strasuns@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=raphael.stolt@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;
as well as URLs for NNTP newsgroup(s).