From: Catalin Marinas <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [StGit PATCH] Convert "pop" to the lib infrastructure
Date: Thu, 2 Apr 2009 17:20:45 +0100 [thread overview]
Message-ID: <b0943d9e0904020920t1a5b87b3i6ac0b37fbcf2ec62@mail.gmail.com> (raw)
In-Reply-To: <20090401120515.GA30918@diana.vm.bytemark.co.uk>
2009/4/1 Karl Hasselström <kha@treskal.com>:
> On 2009-03-31 12:30:27 +0100, Catalin Marinas wrote:
>
>> @@ -47,7 +47,7 @@ test_expect_success 'Try to reset with --hard' '
>> stg reset --hard master.stgit^~1 &&
>> stg status a > actual.txt &&
>> test_cmp expected.txt actual.txt &&
>> - test "$(echo $(stg series))" = "> p1 - p3 - p2"
>> + test "$(echo $(stg series))" = "> p1 - p2 - p3"
>> '
>
> Hmm, why this change in behavior? Something that should be noted in
> the commit message?
>
>> @@ -47,7 +47,7 @@ test_expect_success 'Try to undo with --hard' '
>> stg undo --hard &&
>> stg status a > actual.txt &&
>> test_cmp expected.txt actual.txt &&
>> - test "$(echo $(stg series))" = "> p1 - p3 - p2"
>> + test "$(echo $(stg series))" = "> p1 - p2 - p3"
>> '
>
> And I guess this is the same.
I think we now get a slightly different behaviour because of how the
transactions are generated with the new infrastructure. In the above
case, you have "pop p2 p3" and "push p3", the latter failing. The "pop
p2 p3" command results in the stack being "> p1 - p2 - p3" while "push
p3" performs a single step for pushing and reordering. The old push
caused a reorder followed by a push.
So I think I should place the push changes before the pop ones so that
pop itself doesn't fail.
I'll try to push them tonight as I'll go on holiday soon for two weeks.
--
Catalin
next prev parent reply other threads:[~2009-04-02 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 11:30 [StGit PATCH] Convert "pop" to the lib infrastructure Catalin Marinas
2009-04-01 12:05 ` Karl Hasselström
2009-04-02 16:20 ` Catalin Marinas [this message]
2009-04-03 10:36 ` Karl Hasselström
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=b0943d9e0904020920t1a5b87b3i6ac0b37fbcf2ec62@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.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).