git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>, git@vger.kernel.org
Subject: Re: Random thoughts on "upstream"
Date: Thu, 23 May 2013 10:25:11 -0700	[thread overview]
Message-ID: <7vppwhfw20.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CALkWK0m1x_qrJfQ2Xw3w_kVuM-JHERFukbfxHyR08ODvxysKzw@mail.gmail.com> (Ramkumar Ramachandra's message of "Thu, 23 May 2013 16:12:03 +0530")

Ramkumar Ramachandra <artagnon@gmail.com> writes:

> [remote "theodore"]
>     push = master
>     push = +pu
>
> This means that I will always push master without force and pu with
> force, irrespective of the branch I'm on.
>
> [remote "origin"]
>     push = refs/heads/*:refs/heads/rr/*
>
> This means that I will always push all branches without force with
> rewriting, irrespective of the branch I'm on.

Exactly.  And some people are unhappy about it, because they prefer
to work per-branch basis, as opposed to having to perfect everything
into a publishable state first and then finally push everything out
in one go.

I am not saying default=single would be _the_ single right way to
solve it, but "when you have default=single, remote.$name.push is
used only to describe the mapping, not forcing you to push
everything out at once" is one possible solution to that.

  parent reply	other threads:[~2013-05-23 17:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 17:55 Random thoughts on "upstream" Junio C Hamano
2013-05-16 23:03 ` Felipe Contreras
2013-05-16 23:17   ` Junio C Hamano
2013-05-17  0:00     ` Felipe Contreras
2013-05-17  1:31     ` Junio C Hamano
2013-05-17  1:59       ` Felipe Contreras
2013-05-17  2:00         ` Felipe Contreras
2013-05-17 12:43       ` Ramkumar Ramachandra
2013-05-17 16:45         ` Junio C Hamano
2013-05-17 17:01           ` Ramkumar Ramachandra
2013-05-17 17:51             ` Junio C Hamano
2013-05-18 18:27               ` Ramkumar Ramachandra
2013-05-18 20:07                 ` Ramkumar Ramachandra
2013-05-18 22:36                   ` Felipe Contreras
2013-05-18 22:33                 ` Felipe Contreras
2013-05-19  5:58                 ` Junio C Hamano
2013-05-19 11:44                   ` Ramkumar Ramachandra
2013-05-19 11:48                     ` Felipe Contreras
2013-05-19 11:54                       ` Ramkumar Ramachandra
2013-05-19 12:00                         ` Felipe Contreras
2013-05-20  4:28                     ` Junio C Hamano
2013-05-23 10:42                       ` Ramkumar Ramachandra
2013-05-23 10:53                         ` Felipe Contreras
2013-05-23 17:25                         ` Junio C Hamano [this message]
2013-05-23 17:41                           ` Ramkumar Ramachandra
2013-05-24  6:39                             ` Ramkumar Ramachandra

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=7vppwhfw20.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=artagnon@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    /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).