git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: Jeff King <peff@peff.net>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Johannes Sixt <j.sixt@viscovery.net>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] remote: improve sorting of "configure for git push" list
Date: Sun, 22 Mar 2009 14:58:26 -0700	[thread overview]
Message-ID: <7vk56hdxtp.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 76718490903220747p74cf3704vbbbc085c28a105b2@mail.gmail.com

Jay Soffian <jaysoffian@gmail.com> writes:

> On Sun, Mar 22, 2009 at 4:59 AM, Jeff King <peff@peff.net> wrote:
>> The data structure used to store this list is a string_list
>> of sources with the destination in the util member. The
>> current code just sorts on the source; if a single source is
>> pushed to two different destination refs at a remote, then
>> the order in which they are printed is non-deterministic.
>> ...
> Ack. There is one thing I wonder though. Is this even a sane config?

I do not think of a workflow that this feature is absolutely necessary in
the sense that it cannot be worked around if you removed it, but that is
not what you asked.

I wouldn't be surprised if there are some kernel subsystem maintainers who
usually push to their master but when they push their finished goods to
their for-linus branch make sure they update their master at the same time.
Configuring their local for-linus to push to master and for-linus may be
one way to do so.

In a one-branch project with two people, it is not entirely inconceivable
to arrange for me to push to master and junio while you to push to master
and jay, in order to keep track.

  reply	other threads:[~2009-03-22 22:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 11:42 t5505-remote fails on Windows Johannes Sixt
2009-03-19  4:18 ` Jeff King
2009-03-19  4:43   ` Jeff King
2009-03-19  4:56     ` Jay Soffian
2009-03-19  5:03       ` Jeff King
2009-03-19  7:20     ` Johannes Sixt
2009-03-19 20:04       ` Jeff King
2009-03-19 10:36     ` Johannes Schindelin
2009-03-19 11:02       ` Junio C Hamano
2009-03-19 15:00         ` Jay Soffian
2009-03-19 20:03         ` Jeff King
2009-03-19 23:15           ` Johannes Schindelin
2009-03-22  8:59           ` [PATCH] remote: improve sorting of "configure for git push" list Jeff King
2009-03-22 14:47             ` Jay Soffian
2009-03-22 21:58               ` Junio C Hamano [this message]
2009-03-23  7:56             ` Johannes Sixt
2009-03-23  8:09               ` Junio C Hamano
2009-03-19 19:52       ` t5505-remote fails on Windows 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=7vk56hdxtp.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=jaysoffian@gmail.com \
    --cc=peff@peff.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).