From: Andreas Schwab <schwab@linux-m68k.org>
To: it-developer@abelardolg.com
Cc: git@vger.kernel.org
Subject: Re: A suggestion: more readable human commands
Date: Tue, 15 Jun 2021 13:55:07 +0200 [thread overview]
Message-ID: <87o8c7wdes.fsf@igel.home> (raw)
In-Reply-To: <fa2e886dd03a26c945d9deffe6f96d48@abelardolg.com> (it-developer@abelardolg.com's message of "Tue, 15 Jun 2021 12:51:36 +0200")
On Jun 15 2021, it-developer@abelardolg.com wrote:
> 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>
This is ambigous if a branch or tag named <path_file> or to exists, and
the usual disambiguation using -- will not work.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2021-06-15 11:55 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
2021-06-15 11:55 ` Andreas Schwab [this message]
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=87o8c7wdes.fsf@igel.home \
--to=schwab@linux-m68k.org \
--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).