From: Junio C Hamano <gitster@pobox.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: git@vger.kernel.org, peff@peff.net
Subject: Re: [PATCH v2] doc: remove misleading documentation on pack names
Date: Wed, 22 Jul 2020 14:16:37 -0700 [thread overview]
Message-ID: <xmqqsgdj45e2.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <ab8993fc6840765895ad39c59af1e536582e76d7.camel@sipsolutions.net> (Johannes Berg's message of "Wed, 22 Jul 2020 23:14:03 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> Really all I was trying to do is be a *little* more helpful than just
> point out "the documentation is wrong"...
Thanks.
prev parent reply other threads:[~2020-07-22 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 20:26 [PATCH v2] doc: remove misleading documentation on pack names Johannes Berg
2020-07-22 21:09 ` Junio C Hamano
2020-07-22 21:14 ` Johannes Berg
2020-07-22 21:16 ` Junio C Hamano [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqsgdj45e2.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).