From: sean <seanlkml@sympatico.ca>
To: Junio C Hamano <junkio@cox.net>
Cc: barkalow@iabervon.org, git@vger.kernel.org
Subject: Re: [RFC] Reverting "git push logic change"?
Date: Sun, 22 Jan 2006 16:42:50 -0500 [thread overview]
Message-ID: <BAYC1-PASMTP0532B701820FA4ADB3C640AE110@CEZ.ICE> (raw)
Message-ID: <20060122164250.2c7ec979.seanlkml@sympatico.ca> (raw)
In-Reply-To: <7vu0bw9ch7.fsf@assigned-by-dhcp.cox.net>
On Sun, 22 Jan 2006 13:31:00 -0800
Junio C Hamano <junkio@cox.net> wrote:
> +If you created your shared repository by cloning from somewhere
> +else, you may have the `origin` branch. Your developers
> +typically do not use that branch; remove it. Otherwise, that
> +would be pushed back by the `git push origin` because your
> +developers' repository would surely have `origin` branch to keep
> +track of the shared repository, and would be counted as "exist
> +on both ends".
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.
Sean
next prev parent reply other threads:[~2006-01-22 21:48 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
[not found] ` <20060122164250.2c7ec979.seanlkml@sympatico.ca>
2006-01-22 21:42 ` sean [this message]
2006-01-22 23:09 ` Junio C Hamano
2006-01-23 1:31 ` Junio C Hamano
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=BAYC1-PASMTP0532B701820FA4ADB3C640AE110@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).