From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Junio C Hamano <gitster@pobox.com>,
Derrick Stolee <dstolee@microsoft.com>
Subject: Re: [PATCH v2 0/3] Additional FAQ entries
Date: Thu, 6 Jan 2022 01:58:29 +0000 [thread overview]
Message-ID: <YdZMxeOSFQPYBmZY@camp.crustytoothpaste.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2201041453540.7076@tvgsbejvaqbjf.bet>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On 2022-01-04 at 13:54:52, Johannes Schindelin wrote:
> Hi brian,
>
> On Sun, 7 Nov 2021, brian m. carlson wrote:
>
> > This series introduces some additional Git FAQ entries on various
> > topics. They are all things I've seen in my professional life or on
> > Stack Overflow, so I've written documentation.
> >
> > I've opted not to include backing up repositories in the syncing patch
> > because I think they're separate topics. We could well end up with an
> > additional FAQ entry on that topic, which is left as an exercise for the
> > reader.
>
> Makes sense.
>
> You hinted in the thread that you were planning on submitting a v3. I hope
> that my feedback regarding `core.gitproxy` is still in time for that.
I can definitely include that in v3. I'm hoping I can get to it later
this week or during the weekend before my schedule becomes busy again.
I appreciate the thoughtful comments.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2022-01-06 1:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 22:55 [PATCH v2 0/3] Additional FAQ entries brian m. carlson
2021-11-07 22:55 ` [PATCH v2 1/3] gitfaq: add documentation on proxies brian m. carlson
2021-11-07 23:27 ` Eric Sunshine
2021-11-08 1:53 ` brian m. carlson
2021-11-08 21:24 ` Junio C Hamano
2022-01-04 13:40 ` Johannes Schindelin
2021-11-07 22:55 ` [PATCH v2 2/3] gitfaq: give advice on using eol attribute in gitattributes brian m. carlson
2021-11-07 23:48 ` Eric Sunshine
2021-11-08 2:09 ` brian m. carlson
2021-11-07 22:55 ` [PATCH v2 3/3] gitfaq: add entry about syncing working trees brian m. carlson
2021-11-08 0:12 ` Eric Sunshine
2021-11-08 22:09 ` Junio C Hamano
2021-11-09 0:10 ` Junio C Hamano
2021-11-14 23:40 ` brian m. carlson
[not found] ` <YYmmBMkwy6bpVpzI@camp.crustytoothpaste.net>
2021-11-09 0:02 ` Eric Sunshine
2021-11-08 0:16 ` [PATCH v2 0/3] Additional FAQ entries Eric Sunshine
2022-01-04 13:53 ` Johannes Schindelin
2022-01-04 13:54 ` Johannes Schindelin
2022-01-06 1:58 ` brian m. carlson [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=YdZMxeOSFQPYBmZY@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=bagasdotme@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.