From: Rob Hoelz <rob@hoelz.ro>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Adding a new option to git-push: --(no-)create-branch
Date: Thu, 19 Apr 2012 08:40:56 +0200 [thread overview]
Message-ID: <20120419084056.1a8c1540@hoelz.ro> (raw)
In-Reply-To: <7vk41cim4i.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
I suppose it would be...I may just need to retrain my fingers! =)
On Wed, 18 Apr 2012 17:46:53 -0700
Junio C Hamano <gitster@pobox.com> wrote:
> 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?
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-04-19 6:41 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
2012-04-19 6:40 ` Rob Hoelz [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=20120419084056.1a8c1540@hoelz.ro \
--to=rob@hoelz.ro \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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