All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: sean <seanlkml@sympatico.ca>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Reverting "git push logic change"?
Date: Sun, 22 Jan 2006 17:31:22 -0800	[thread overview]
Message-ID: <7vacdnafx1.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 7vpsmjamgw.fsf@assigned-by-dhcp.cox.net

Junio C Hamano <junkio@cox.net> writes:

> sean <seanlkml@sympatico.ca> writes:
>
>> What about just always excluding the origin branch from being 
>> implicitly pushed; even if it does exist in both repositories?
>> In the rare cases where it is actually desired to be pushed,
>> it can be done explicitly.
>
> The problem is "origin" is just a Porcelain convention and we
> would not want to teach that to the core level, so that will not
> fly.

One improvement that can be done is to update "git clone --bare"
so that it does not create "origin", which is more or less
pointless for such a "distribution point" repository.

This reminds me that I need to deprecate --naked and introduce --bare
to the clone command...

  reply	other threads:[~2006-01-23  1:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 22:53 "git push" logic changed? Greg KH
2006-01-21  0:03 ` Junio C Hamano
2006-01-21  0:15   ` Greg KH
2006-01-21  0:54     ` Junio C Hamano
2006-01-21  0:59     ` Junio C Hamano
2006-01-21  7:46     ` [RFC] Reverting "git push logic change"? Junio C Hamano
2006-01-22 19:09       ` Daniel Barkalow
2006-01-22 20:31         ` Junio C Hamano
2006-01-22 21:31           ` Junio C Hamano
2006-01-22 21:42             ` sean
2006-01-22 21:42               ` sean
2006-01-22 23:09                 ` Junio C Hamano
2006-01-23  1:31                   ` Junio C Hamano [this message]
2006-01-24  5:05       ` Greg KH

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=7vacdnafx1.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=seanlkml@sympatico.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.