All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2011, #13; Mon, 30)
Date: Mon, 30 May 2011 23:21:31 -0700	[thread overview]
Message-ID: <7v39jvl79w.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4DE4857A.70605@viscovery.net> (Johannes Sixt's message of "Tue, 31 May 2011 08:06:50 +0200")

Johannes Sixt <j.sixt@viscovery.net> writes:

> ... But as far as I am concerned, I do not mind backing out changes
> that break on Windows until a solution is found.
>
> [*] I do include cooking topics where I think that there is a chance that
> they break on Windows.

Very much appreciated. We want more people to help keeping the tip of
"master" stable by running "next", or selected topics in it that may
affect you in the future, like you do. Hearing that "master" is broken
due to recent merge of topic X is, while better than hearing the same
after the tip of "master" is tagged, a bit saddening, as the reason "next"
exists in the first place is exactly to prevent such accidents by catching
buggy topics while they are in "next".

Thanks.

      reply	other threads:[~2011-05-31  6:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30  8:16 What's cooking in git.git (May 2011, #13; Mon, 30) Junio C Hamano
2011-05-30 12:08 ` Ævar Arnfjörð Bjarmason
2011-05-30 12:19   ` Johannes Sixt
2011-05-30 13:55     ` Ævar Arnfjörð Bjarmason
2011-05-30 18:17   ` Junio C Hamano
2011-05-31  6:06     ` Johannes Sixt
2011-05-31  6:21       ` Junio C Hamano [this message]

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=7v39jvl79w.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.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 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.