From: Junio C Hamano <gitster@pobox.com>
To: Rob Hoelz <rob@hoelz.ro>
Cc: git@vger.kernel.org
Subject: Re: Adding a new option to git-push: --(no-)create-branch
Date: Wed, 18 Apr 2012 17:46:53 -0700 [thread overview]
Message-ID: <7vk41cim4i.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4F8F3A25.1080407@hoelz.ro> (Rob Hoelz's message of "Thu, 19 Apr 2012 00:03:17 +0200")
Rob Hoelz <rob@hoelz.ro> writes:
> However, I will often make a typo like this:
>
> git push origin master:msater
Why isn't "git push origin master" explicit enough?
next prev parent reply other threads:[~2012-04-19 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 22:03 Adding a new option to git-push: --(no-)create-branch Rob Hoelz
2012-04-19 0:46 ` Junio C Hamano [this message]
2012-04-19 6:40 ` Rob Hoelz
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=7vk41cim4i.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rob@hoelz.ro \
/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