From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: git@vger.kernel.org, Matthieu.Moy@grenoble-inp.fr, j6t@kdbg.org,
johannes.schindelin@gmail.com, Lucien.Kong@ensimag.imag.fr
Subject: Re: [PATCH] rebase -x: do not die without -i
Date: Thu, 17 Mar 2016 00:50:09 -0700 [thread overview]
Message-ID: <xmqq4mc535n2.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1458177584-11378-1-git-send-email-sbeller@google.com> (Stefan Beller's message of "Wed, 16 Mar 2016 18:19:44 -0700")
Stefan Beller <sbeller@google.com> writes:
> In the later steps of preparing a patch series I do not want to edit the
> patches any more, but just make sure the test suite passes after each
> patch. Currently I would run
>
> EDITOR=true git rebase -i <anchor> -x "make test"
Hmm, I guess that may "work" but it sounds like quite a roundabout
way to "test all commits". "rebase" is about replaying history to
end up with a set of newly minted commits, and being able to poke at
the state each commit records in the working tree is a side effect.
"rebase -i" may use the same commit object if you didn't actually
make new commit as an optimization, but otherwise, it is like going
through pages of a book, tearing each page to examine it, and
replacing each page with a photocopy of it before going to examine
the next page. Which makes me feel somewhat dirty X-<.
In other words, that looks like a workaround for not having
$ git for-each-rev -x "$command" old..new
where you can write "sh -c 'git checkout $1 && make test' -" as
your $command.
next prev parent reply other threads:[~2016-03-17 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 1:19 [PATCH] rebase -x: do not die without -i Stefan Beller
2016-03-17 6:20 ` Johannes Sixt
2016-03-17 6:48 ` Johannes Schindelin
2016-03-17 7:50 ` Junio C Hamano [this message]
2016-03-17 13:11 ` Johannes Schindelin
2016-03-17 18:10 ` Junio C Hamano
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=xmqq4mc535n2.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Lucien.Kong@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=johannes.schindelin@gmail.com \
--cc=sbeller@google.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.