From: Diggory Hardy <lists@dhardy.name>
To: git@vger.kernel.org
Subject: git push remote syntax
Date: Mon, 07 Nov 2016 13:49:40 +0000 [thread overview]
Message-ID: <1613741.x6i0st30av@localhost.localdomain> (raw)
Dear all,
One thing I find a little frustrating about git is that the syntax needed
differs by command. I wish the 'remote/branch' syntax was more universal:
> git pull myremote/somebranch
complains about the syntax; IMO it should either pull from that branch (and
merge if necessary) or complain instead that pulling from a different branch
is not supported (and suggest using merge).
> git push myremote/somebranch
should push there, i.e. be equivalent to
> git push myremote HEAD:somebranch
These are just some comments about how I think git could be made easier to
use. Apologies if the suggestions have already been discussed before.
Regards,
D Hardy
next reply other threads:[~2016-11-07 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 13:49 Diggory Hardy [this message]
2016-11-07 21:01 ` git push remote syntax Jeff King
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=1613741.x6i0st30av@localhost.localdomain \
--to=lists@dhardy.name \
--cc=git@vger.kernel.org \
/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