From: Junio C Hamano <gitster@pobox.com>
To: Pratyush Yadav <me@yadavpratyush.com>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH] Documentation: update the location of the git-gui repo
Date: Sat, 05 Oct 2019 18:02:01 +0900 [thread overview]
Message-ID: <xmqqr23r7egm.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20191004222956.12341-1-me@yadavpratyush.com> (Pratyush Yadav's message of "Sat, 5 Oct 2019 03:59:56 +0530")
Pratyush Yadav <me@yadavpratyush.com> writes:
> Signed-off-by: Pratyush Yadav <me@yadavpratyush.com>
> ---
> Documentation/git-gui.txt | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/git-gui.txt b/Documentation/git-gui.txt
> index 5f93f8003d..98337b69f1 100644
> --- a/Documentation/git-gui.txt
> +++ b/Documentation/git-gui.txt
> @@ -114,13 +114,9 @@ of end users.
>
> A 'git gui' development repository can be obtained from:
>
> - git clone git://repo.or.cz/git-gui.git
> + git clone https://github.com/prati0100/git-gui.git
>
> -or
> -
> - git clone http://repo.or.cz/r/git-gui.git
> -
> -or browsed online at http://repo.or.cz/w/git-gui.git/[].
> +or browsed online at https://github.com/prati0100/git-gui[].
>
> GIT
> ---
These days, unlike back when the original of this manpage was
written, we can expect far more people know Git, GitHub and what to
do with it when they see a GitHub URL to a repository. Hence, a
single GitHub repository URL is sufficient, without "git clone" or
mention of "browsed online", I would think.
IOW, all of the above can now be just two lines, e.g.
The official repository of `git gui` project can be found at
https://github.com/prati0100/git-gui.git/
Thanks.
next prev parent reply other threads:[~2019-10-05 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 22:29 [PATCH] Documentation: update the location of the git-gui repo Pratyush Yadav
2019-10-05 9:02 ` Junio C Hamano [this message]
2019-10-05 12:57 ` [PATCH v2] " Pratyush Yadav
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=xmqqr23r7egm.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@yadavpratyush.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.
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).