From: Bagas Sanjaya <bagasdotme@gmail.com>
To: it-developer@abelardolg.com, git@vger.kernel.org
Subject: Re: A suggestion: more readable human commands
Date: Tue, 15 Jun 2021 17:59:04 +0700 [thread overview]
Message-ID: <c3855aea-6cbd-af30-7791-07c212c52bbd@gmail.com> (raw)
In-Reply-To: <fa2e886dd03a26c945d9deffe6f96d48@abelardolg.com>
On 15/06/21 17.51, it-developer@abelardolg.com wrote:
> Hi there,
>
> I would like to suggest you a new improvement.
>
> Why not adding a new layer of abstraction for commands or to make more
> explicitly the commands?
>
> For instance:
>
> To merge a single file from one branch to another:
>
> git checkout <branch_name> <path_to_file> --patch
>
> would be like more readable human like this:
>
> git merge <path_file> to <dst_branch>
>
> It uses a more natural language.
>
> Best regards.
What workflow you do so that you need to merge single file?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-06-15 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 10:51 A suggestion: more readable human commands it-developer
2021-06-15 10:59 ` Bagas Sanjaya [this message]
2021-06-15 11:55 ` Andreas Schwab
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=c3855aea-6cbd-af30-7791-07c212c52bbd@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=it-developer@abelardolg.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).