From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH 1/3] docs: adjust for the recent rename of `pu` to `seen`
Date: Tue, 23 Jun 2020 22:31:06 +0700 [thread overview]
Message-ID: <20200623153106.GB20455@danh.dev> (raw)
In-Reply-To: <dc6f97129019e9176d91c77576a84549c00a74b5.1592924655.git.gitgitgadget@gmail.com>
Hi Dscho,
On 2020-06-23 15:04:13+0000, Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com> wrote:
> diff --git a/Documentation/git-ls-remote.txt b/Documentation/git-ls-remote.txt
> index 0a5c8b7d493..492e573856f 100644
> --- a/Documentation/git-ls-remote.txt
> +++ b/Documentation/git-ls-remote.txt
> @@ -101,9 +101,9 @@ f25a265a342aed6041ab0cc484224d9ca54b6f41 refs/tags/v0.99.1
> 7ceca275d047c90c0c7d5afb13ab97efdf51bd6e refs/tags/v0.99.3
> c5db5456ae3b0873fc659c19fafdde22313cc441 refs/tags/v0.99.2
> 0918385dbd9656cab0d1d81ba7453d49bbc16250 refs/tags/junio-gpg-pub
> -$ git ls-remote http://www.kernel.org/pub/scm/git/git.git master pu rc
> +$ git ls-remote http://www.kernel.org/pub/scm/git/git.git master seen rc
rc is not with us anymore.
Should we replace it with next, too?
> 5fe978a5381f1fbad26a80e682ddd2a401966740 refs/heads/master
> -c781a84b5204fb294c9ccc79f8b3baceeb32c061 refs/heads/pu
> +c781a84b5204fb294c9ccc79f8b3baceeb32c061 refs/heads/seen
> $ git remote add korg http://www.kernel.org/pub/scm/git/git.git
> $ git ls-remote --tags korg v\*
> d6602ec5194c87b0fc87103ca4d67251c76f233a refs/tags/v0.99
--
Danh
next prev parent reply other threads:[~2020-06-23 15:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 15:04 [PATCH 0/3] Accommodate for pu having been renamed to seen Johannes Schindelin via GitGitGadget
2020-06-23 15:04 ` [PATCH 1/3] docs: adjust for the recent rename of `pu` to `seen` Johannes Schindelin via GitGitGadget
2020-06-23 15:31 ` Đoàn Trần Công Danh [this message]
2020-06-23 19:31 ` Junio C Hamano
2020-06-23 21:32 ` Johannes Schindelin
2020-06-24 0:46 ` Đoàn Trần Công Danh
2020-06-23 15:04 ` [PATCH 2/3] docs: adjust the technical overview for the rename `pu` -> `seen` Johannes Schindelin via GitGitGadget
2020-06-23 15:04 ` [PATCH 3/3] tests: reference `seen` wherever `pu` was referenced Johannes Schindelin via GitGitGadget
2020-06-24 14:48 ` [PATCH v2 0/3] Accommodate for pu having been renamed to seen Johannes Schindelin via GitGitGadget
2020-06-24 14:48 ` [PATCH v2 1/3] docs: adjust for the recent rename of `pu` to `seen` Johannes Schindelin via GitGitGadget
2020-06-24 15:07 ` Denton Liu
2020-06-24 14:48 ` [PATCH v2 2/3] docs: adjust the technical overview for the rename `pu` -> `seen` Johannes Schindelin via GitGitGadget
2020-06-24 14:48 ` [PATCH v2 3/3] tests: reference `seen` wherever `pu` was referenced Johannes Schindelin via GitGitGadget
2020-06-24 15:24 ` [PATCH v2 0/3] Accommodate for pu having been renamed to seen Denton Liu
2020-06-24 15:42 ` Junio C Hamano
2020-06-29 13:40 ` Johannes Schindelin
2020-06-24 15:38 ` Junio C Hamano
2020-06-24 17:05 ` Junio C Hamano
2020-06-24 17:24 ` Denton Liu
2020-06-24 17:38 ` Junio C Hamano
2020-06-29 14:05 ` Johannes Schindelin
2020-06-25 12:18 ` [PATCH v3 " Johannes Schindelin via GitGitGadget
2020-06-25 12:18 ` [PATCH v3 1/3] docs: adjust for the recent rename of `pu` to `seen` Johannes Schindelin via GitGitGadget
2020-06-25 12:18 ` [PATCH v3 2/3] docs: adjust the technical overview for the rename `pu` -> `seen` Johannes Schindelin via GitGitGadget
2020-06-25 12:18 ` [PATCH v3 3/3] tests: reference `seen` wherever `pu` was referenced Johannes Schindelin via GitGitGadget
2020-06-25 16:22 ` [PATCH v3 0/3] Accommodate for pu having been renamed to seen Junio C Hamano
2020-06-29 14:07 ` Johannes Schindelin
2020-06-30 16:03 ` Junio C Hamano
2020-07-01 10:42 ` Johannes Schindelin
2020-06-26 9:06 ` Update ProGit for pu -> seen change? (was Re: [PATCH v3 0/3] Accommodate for pu having been renamed to seen) Kaartic Sivaraam
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=20200623153106.GB20455@danh.dev \
--to=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
/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).