From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 0/3] fix interactive rebase short SHA-1 collision bug
Date: Mon, 26 Aug 2013 00:19:22 -0700 [thread overview]
Message-ID: <xmqqbo4kkjgl.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1377303042-50868-1-git-send-email-sunshine@sunshineco.com> (Eric Sunshine's message of "Fri, 23 Aug 2013 20:10:39 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
> ... when 'next' is ready to be rewound after 1.8.4
> is released, a replacement to the original series should be sent with
> all the incremental patches squashed in.
It was more like "could, if you want to help us keep clean history
going forward", rather than "should" ;-) Thanks for resending.
I've locally queued this series after seeing the end-result matches
what has been cooking.
Traditionally we waited for a few days after a release to see if we
do not receive regression reports that require us to issue brown
paper bag fixes before rewinding "next" and opening a new cycle. I
am hoping that it will happen in a few days.
My responses may be slower than usual today (i.e. Monday 26th), as I
would need to be sitting in dentist's for a few hours.
prev parent reply other threads:[~2013-08-26 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-24 0:10 [PATCH v2 0/3] fix interactive rebase short SHA-1 collision bug Eric Sunshine
2013-08-24 0:10 ` [PATCH v2 1/3] t3404: make tests more self-contained Eric Sunshine
2013-08-24 0:10 ` [PATCH v2 2/3] t3404: rebase -i: demonstrate short SHA-1 collision Eric Sunshine
2013-08-25 6:16 ` Jonathan Nieder
2013-08-24 0:10 ` [PATCH v2 3/3] rebase -i: fix " Eric Sunshine
2013-08-26 7:19 ` 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=xmqqbo4kkjgl.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
/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.