From: Paolo Bonzini <bonzini@gnu.org>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Marc Branchaud" <marcnarc@xiplink.com>,
git@vger.kernel.org
Subject: Re: [RFC/PATCH] rebase -i: add run command to launch a shell command
Date: Mon, 02 Aug 2010 17:04:08 +0200 [thread overview]
Message-ID: <4C56DE68.7010906@gnu.org> (raw)
In-Reply-To: <vpqwrs9nxi5.fsf@bauges.imag.fr>
On 08/02/2010 12:02 PM, Matthieu Moy wrote:
> I think this makes more sense for the user, and I've actually already
> been biten by the old behavior, running "rebase -i" from a doc/
> subdirectory, and wondering why my "exec make" was rebuilding the
> code itself.
I think it's a matter of habits, and I would surely be bitten more by
the opposite problem: when I'm usually ready to rebase and test I'm
likely to be in src/ (for packages that have one such directory) or tests/.
cd to the top-level repository is a logical choice since rebase is a
repository-wide command (even though the particular set of commits might
touch only a part of it). It is easier to implement, does not have any
problem with conflicts or otherwise with deletion, and easier to
document as well.
If you decide to go with the other choice, however, I would _strongly_
suggest failing if the directory not exists. After all most of the time
the command ("make" for example) will be pretty unlikely to succeed.
Paolo
next prev parent reply other threads:[~2010-08-02 15:04 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
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 ` Paolo Bonzini [this message]
2010-08-02 21:15 ` [RFC/PATCH] rebase -i: add run command to launch a shell command 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=4C56DE68.7010906@gnu.org \
--to=bonzini@gnu.org \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=marcnarc@xiplink.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 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).