From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Gerrit Pape <pape@smarden.org>, git@vger.kernel.org
Subject: Re: [PATCH] Add test for rebase -i with commits that do not pass pre-commit
Date: Mon, 28 Jan 2008 21:24:45 -0500 [thread overview]
Message-ID: <20080129022445.GG24004@spearce.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0801281632300.23907@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> This accompanies c5b09feb(Avoid update hook during git-rebase --interactive)
wtf was I smoking when I wrote that commit subject line? Its not
the update hook we're avoiding here. But yea, I thought this looked
like something I had worked on recently. :)
> to prove that Debian's Bug#458782 (git-core: git-rebase doesn't work when
> trying to squash changes into commits created with --no-verify) is indeed
> fixed now.
--
Shawn.
prev parent reply other threads:[~2008-01-29 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 15:42 git-rebase doesn't work when trying to squash changes into commits created with --no-verify Gerrit Pape
2008-01-28 16:33 ` [PATCH] Add test for rebase -i with commits that do not pass pre-commit Johannes Schindelin
2008-01-29 2:24 ` Shawn O. Pearce [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=20080129022445.GG24004@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pape@smarden.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).