From: Philip Oakley <philipoakley@iee.email>
To: GitList <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH v2] Doc: Bundle file usage
Date: Wed, 16 Oct 2019 11:15:47 +0100 [thread overview]
Message-ID: <59958c50-cbcb-ae9b-614f-ba28221f41ed@iee.email> (raw)
In-Reply-To: <20191016095737.1588-1-philipoakley@iee.email>
On 16/10/2019 10:57, Philip Oakley wrote:
> From: Philip Oakley <philipoakley@iee.org>
Oops - the From: line still has my old email address. Is a resend
preferred, or can it be fixed locally?
P.
> Git URLs can accept bundle files for fetch, pull and clone, include
> in that section. Include git clone in the bundle usage description.
> Correct the quoting of <git-rev-list-args>.
> Detail the <git-rev-list-args> options for cloning a complete repo.
>
> Signed-off-by: Philip Oakley <philipoakley@iee.email>
> ---
>
> This takes up the advice from peff in
> https://public-inbox.org/git/20191011161112.GA19741@sigill.intra.peff.net/
> from the original v1 in 2012(!)
> https://public-inbox.org/git/1348010734-664-2-git-send-email-philipoakley@iee.org/
>
> Hopefully this covers Junio's concerns from that time.
next prev parent reply other threads:[~2019-10-16 10:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 23:25 [PATCHv2 1/8] Doc: Bundle file usage Philip Oakley
2012-09-18 23:55 ` Junio C Hamano
2019-10-16 9:57 ` [PATCH v2] " Philip Oakley
2019-10-16 10:15 ` Philip Oakley [this message]
2019-10-16 21:09 ` Jeff King
2019-10-17 2:54 ` Junio C Hamano
2019-10-18 15:15 ` [PATCH v3] " Philip Oakley
2019-10-18 18:15 ` Pratyush Yadav
2019-10-18 19:58 ` Philip Oakley
2019-10-18 20:30 ` [PATCH v4] " Philip Oakley
2019-10-20 1:10 ` Jeff King
2019-10-20 10:49 ` Philip Oakley
2019-10-20 11:03 ` [PATCH v5] " Philip Oakley
2019-10-21 2:48 ` Junio C Hamano
2019-10-21 3:16 ` Jeff King
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=59958c50-cbcb-ae9b-614f-ba28221f41ed@iee.email \
--to=philipoakley@iee.email \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).