git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Nanako Shiraishi <nanako3@lavabit.com>, git@vger.kernel.org
Subject: Re: push.default, was Re: What's cooking in git.git (Mar 2009, #04; Sat, 14)
Date: Tue, 17 Mar 2009 18:05:25 -0700	[thread overview]
Message-ID: <7vwsanod2i.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0903180138210.10279@pacific.mpi-cbg.de> (Johannes Schindelin's message of "Wed, 18 Mar 2009 01:40:39 +0100 (CET)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> In my git.git clone on one machine, I have remote.orcz.push = master.  I 
> cloned it.  There, "git push" does something different.
>
> Inconsistent right there, correct?  Without any change to git.git.

You must be smoking something potent.  It's a nonsense argument and you
know it.

In your git.git clone on one machine, you have some setting.

You cloned it to one machine some time ago.  It behave differently and
that is something that has always been true, and you know it.  Repository
configuration is private.

You clone it to another today.  Now the new clone, without any
configuration, will behave differently from the other clone, that you
haven't done any funny configuration.

That's inconsistent.

  reply	other threads:[~2009-03-18  1:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15  6:28 What's cooking in git.git (Mar 2009, #04; Sat, 14) Junio C Hamano
2009-03-16 23:11 ` Daniel Barkalow
2009-03-17  0:19   ` Junio C Hamano
2009-03-17 10:28 ` push.default, was " Johannes Schindelin
2009-03-17 21:30   ` Nanako Shiraishi
2009-03-17 22:53     ` Johannes Schindelin
2009-03-17 23:47       ` Junio C Hamano
2009-03-18  0:40         ` Johannes Schindelin
2009-03-18  1:05           ` Junio C Hamano [this message]
2009-03-17 10:31 ` notes, " Johannes Schindelin

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=7vwsanod2i.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=nanako3@lavabit.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).