From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: "Santi Béjar" <santi@agolina.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] rebase -i: add run command to launch a shell command
Date: Fri, 30 Jul 2010 12:04:24 +0200 [thread overview]
Message-ID: <vpq1valffpz.fsf@bauges.imag.fr> (raw)
In-Reply-To: <vpq1van3cnl.fsf@bauges.imag.fr> (Matthieu Moy's message of "Wed\, 28 Jul 2010 16\:26\:54 +0200")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> Santi Béjar <santi@agolina.net> writes:
>
>> $ git run HEAD^4.. command arguments
>>
>> (I'm not quite sure about the syntax). Something like "git bisect run"
>> but for all the commits in the range.
>>
>> I know you said "given points in history", maybe each approach is
>> useful for each use case.
>
> Yes, I think both approaches make sense.
I started playing with the patch, and I'm already starting to love
it ;-). For example
pick <commit1>
fixup <commit4>
run make
pick <commit2>
pick <commit3>
...
Just does "the right thing": it checks that the fixup doesn't break
the commit (which is really not only a new state, but also a new
patch, so it can really break), but doesn't spend too much time
re-checking <commit2> and <commit3> (which are new states, but much
more trustworthy than the fixup since the patches are really the
same. I may check them later, but don't want to lose time with them
while hacking).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2010-07-30 10:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 13:29 [RFC/PATCH] rebase -i: add run command to launch a shell command Matthieu Moy
2010-07-28 14:12 ` Santi Béjar
2010-07-28 14:26 ` Matthieu Moy
2010-07-30 10:04 ` Matthieu Moy [this message]
2010-07-30 14:51 ` Marc Branchaud
2010-07-30 15:24 ` Matthieu Moy
2010-07-30 18:26 ` Neal Kreitzinger
2010-07-31 13:27 ` Matthieu Moy
2010-07-31 13:56 ` Ævar Arnfjörð Bjarmason
2010-07-31 14:25 ` Miles Bader
2010-08-02 10:02 ` Matthieu Moy
2010-08-02 10:03 ` [PATCH] rebase -i: add exec " Matthieu Moy
2010-08-02 12:30 ` Jared Hance
2010-08-02 15:51 ` Ævar Arnfjörð Bjarmason
2010-08-06 21:07 ` Johannes Sixt
2010-08-07 8:48 ` Matthieu Moy
2010-08-07 8:56 ` [PATCH 1/2 (new version)] " Matthieu Moy
2010-08-07 8:56 ` [PATCH 2/2] test-lib: user-friendly alternatives to test [!] [-d|-f] Matthieu Moy
2010-08-02 15:04 ` [RFC/PATCH] rebase -i: add run command to launch a shell command Paolo Bonzini
2010-08-02 21:15 ` Junio C Hamano
2010-08-03 6:37 ` Matthieu Moy
2010-08-03 8:47 ` Kris Shannon
2010-08-03 9:16 ` Matthieu Moy
2010-07-31 15:28 ` Paolo Bonzini
2010-07-31 15:52 ` Ævar Arnfjörð Bjarmason
2010-07-31 18:54 ` Jared Hance
2010-07-31 14:40 ` Jared Hance
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=vpq1valffpz.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=santi@agolina.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 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).