git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: markus.heidelberg@web.de, Finn Arne Gangstad <finnag@pvv.org>,
	git@vger.kernel.org, John Tapsell <johnflux@gmail.com>,
	Andreas Ericsson <ae@op5.se>
Subject: Re: [RFC PATCH] git push: Push nothing if no refspecs are given or  configured
Date: Fri, 6 Mar 2009 12:17:57 +0100	[thread overview]
Message-ID: <fabb9a1e0903060317s6bb4644bvb4dbf0b9432ba58a@mail.gmail.com> (raw)
In-Reply-To: <7v4oy7szze.fsf@gitster.siamese.dyndns.org>

Heya,

On Fri, Mar 6, 2009 at 11:32, Junio C Hamano <gitster@pobox.com> wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> On Thu, 5 Mar 2009, Sverre Rabbelier wrote:
>>> Right, I'd like to be able to do:
>>> $ git config push.iamnotretarded true
>>> $ git push
>>
>> LOL!  Sverre, you have a way to crack me up...

Hehe, good, never hurts to add some humor to this list every now and then ;).

> I found it amusing, too.

I think that humor at times is an effective way to convey your point
while and at the same time keeping the tone light :).

> It may have some correlation with how well organized your work habit is,
> but I do not think it has much correlation with being retarded.  It is
> more about "'matching refs' is the perfect default for _my_ use pattern,
> don't mess with it, please".

For me the reason 'git push' works well for me is that origin is
repo.or.cz and I use the repo there just to synch my changes between
my laptop and my pc (and to keep a backup). I reckon there are other
workflows for which it makes sense to use 'git push' directly :).

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2009-03-06 11:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 22:15 [RFC PATCH] git push: Push nothing if no refspecs are given or configured Finn Arne Gangstad
2009-03-05 22:18 ` Sverre Rabbelier
2009-03-05 22:22   ` Markus Heidelberg
2009-03-05 22:25     ` Markus Heidelberg
2009-03-05 22:26       ` Sverre Rabbelier
2009-03-06 10:24         ` Johannes Schindelin
2009-03-06 10:32           ` Junio C Hamano
2009-03-06 11:17             ` Sverre Rabbelier [this message]
2009-03-06 11:48             ` Finn Arne Gangstad
2009-03-06 12:07               ` Johannes Schindelin
2009-03-06 13:58                 ` Finn Arne Gangstad
2009-03-06 15:25                 ` Jakub Narebski
2009-03-06 17:17                   ` Junio C Hamano
2009-03-07  2:06                     ` Johannes Schindelin
2009-03-06 23:00                   ` Johannes Schindelin
2009-03-06 12:26               ` John Tapsell
2009-03-06 15:27                 ` Jakub Narebski
2009-03-05 22:43 ` Junio C Hamano
2009-03-06 10:37 ` Johannes Schindelin
2009-03-09 20:39   ` Markus Heidelberg
2009-03-09 20:48     ` Johannes Schindelin
2009-03-09 21:10       ` Markus Heidelberg
2009-03-09 21:10       ` 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=fabb9a1e0903060317s6bb4644bvb4dbf0b9432ba58a@mail.gmail.com \
    --to=srabbelier@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ae@op5.se \
    --cc=finnag@pvv.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johnflux@gmail.com \
    --cc=markus.heidelberg@web.de \
    /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).