From: "Santi Béjar" <santi@agolina.net>
To: Rustom Mody <rustompmody@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: how to reorder commits
Date: Mon, 20 Jul 2009 18:16:08 +0200 [thread overview]
Message-ID: <adf1fd3d0907200916x752cba3cw901965788acae0c5@mail.gmail.com> (raw)
In-Reply-To: <f46c52560907200901w67edbbdcpe405f28d98953354@mail.gmail.com>
2009/7/20 Rustom Mody <rustompmody@gmail.com>:
> On Mon, Jul 20, 2009 at 9:07 PM, Santi Béjar<santi@agolina.net> wrote:
>> But normally you reorder "changes", not trees.
>
> Which may not always be conflict-free?
No. But the fact that there is no porcelain way to do it may show that
reordering trees is not what you normally want, even if reordering
trees is conflict-free.
HTH,
Santi
next prev parent reply other threads:[~2009-07-20 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 15:07 how to reorder commits Rustom Mody
2009-07-20 15:37 ` Santi Béjar
2009-07-20 16:01 ` Rustom Mody
2009-07-20 16:16 ` Santi Béjar [this message]
[not found] ` <873a8r132o.fsf@krank.kagedal.org>
2009-07-21 7:53 ` Rustom Mody
2009-07-20 21:27 ` Daniel Barkalow
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=adf1fd3d0907200916x752cba3cw901965788acae0c5@mail.gmail.com \
--to=santi@agolina.net \
--cc=git@vger.kernel.org \
--cc=rustompmody@gmail.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).