From: Eric Sunshine <sunshine@sunshineco.com>
To: Dongcan Jiang <dongcan.jiang@gmail.com>
Cc: "Git List" <git@vger.kernel.org>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH v2/GSoC/RFC] fetch: git fetch --deepen
Date: Sun, 22 Mar 2015 15:15:20 -0400 [thread overview]
Message-ID: <CAPig+cSSQaMyW4fbb0guBqJ---VAG8m4trt2a52qLYAANT01og@mail.gmail.com> (raw)
In-Reply-To: <39ef84113d77ee6fa371ac2f23bbb0ef321323ba.1427031746.git.dongcan.jiang@gmail.com>
On Sun, Mar 22, 2015 at 11:24 AM, Dongcan Jiang <dongcan.jiang@gmail.com> wrote:
> This patch is just for discusstion. An option --deepen is added to
> 'git fetch'. When it comes to '--deepen', git should fetch N more
> commits ahead the local shallow commit, where N is indicated by
> '--depth=N'. [1]
> Signed-off-by: Dongcan Jiang <dongcan.jiang@gmail.com>
> ---
> diff --git a/t/t5510-fetch.sh b/t/t5510-fetch.sh
> index d78f320..3b960c8 100755
> --- a/t/t5510-fetch.sh
> +++ b/t/t5510-fetch.sh
> @@ -708,4 +708,16 @@ test_expect_success 'fetching a one-level ref works' '
> )
> '
>
> +test_expect_success 'fetching deepen' '
> + git clone . deepen --depth=1 && (
Quoting Junio[1]: "...make sure tests serve as good examples, tests
should stick to 'options first and then arguments'..."
> + cd deepen &&
> + git fetch .. foo --depth=1
See [1].
> + git show foo
> + test_must_fail git show foo~
> + git fetch .. foo --depth=1 --deepen
See [1].
> + git show foo~
> + test_must_fail git show foo~2
Mentioned previously[2]: Broken &&-chain throughout this test.
> + )
> +'
> +
> test_done
[1]: http://article.gmane.org/gmane.comp.version-control.git/265248
[2]: http://article.gmane.org/gmane.comp.version-control.git/265419
next prev parent reply other threads:[~2015-03-22 19:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 13:04 [PATCH/GSoC/RFC] fetch: git fetch --deepen Dongcan Jiang
2015-03-13 19:42 ` Eric Sunshine
2015-03-16 16:04 ` Dongcan Jiang
2015-03-14 5:35 ` Junio C Hamano
2015-03-14 10:38 ` Duy Nguyen
2015-03-14 22:07 ` Junio C Hamano
2015-03-16 16:08 ` Dongcan Jiang
2015-03-14 10:56 ` Duy Nguyen
2015-03-16 16:10 ` Dongcan Jiang
2015-03-17 10:44 ` Duy Nguyen
2015-03-17 12:00 ` Dongcan Jiang
2015-03-22 15:24 ` [PATCH v2/GSoC/RFC] " Dongcan Jiang
2015-03-22 19:15 ` Eric Sunshine [this message]
2015-03-22 23:23 ` Duy Nguyen
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=CAPig+cSSQaMyW4fbb0guBqJ---VAG8m4trt2a52qLYAANT01og@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=dongcan.jiang@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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).