git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Kevin Bracey <kevin@bracey.fi>
Cc: git@vger.kernel.org
Subject: Re: --simplify-merges breakage
Date: Mon, 08 Apr 2013 12:54:11 -0700	[thread overview]
Message-ID: <7vfvz0x0gs.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <516313D3.2050309@bracey.fi> (Kevin Bracey's message of "Mon, 08 Apr 2013 22:00:35 +0300")

Kevin Bracey <kevin@bracey.fi> writes:

> Commit 4b7f53d ("simplify-merges: drop merge from irrelevant side
> branch") appears to have broken simplify-merges.
>
> ... now I see the "report problems
> immediately" message on the recent merge of that change.

I hope more people now see why we would like to see more people try
'next' regularly.

Will revert it for now, but that would mean side histories like gitk's
will keep showing up in the simplified view.

      reply	other threads:[~2013-04-08 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 19:00 --simplify-merges breakage Kevin Bracey
2013-04-08 19:54 ` 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=7vfvz0x0gs.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=kevin@bracey.fi \
    /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).