git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karl Wiberg <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org, "Gustav Hållberg" <gustav@virtutech.com>
Subject: Re: [RFC PATCH] Record a single transaction for conflicting push  operations
Date: Sun, 20 Dec 2009 00:50:03 +0100	[thread overview]
Message-ID: <b8197bcb0912191550u300a9c20o351eba66c85292bb@mail.gmail.com> (raw)
In-Reply-To: <b0943d9e0912180749ga8857d9j975e119937db9674@mail.gmail.com>

On Fri, Dec 18, 2009 at 4:49 PM, Catalin Marinas
<catalin.marinas@gmail.com> wrote:

> @@ -371,12 +369,10 @@ class StackTransaction(object):
>             # We've just caused conflicts, so we must allow them in
>             # the final checkout.
>             self.__allow_conflicts = lambda trans: True
> -
> -            # Save this update so that we can run it a little later.
> -            self.__conflicting_push = update
> +            self.__patches = _TransPatchMap(self.__stack)
> +            update()
>             self.__halt("%d merge conflict(s)" % len(self.__conflicts))
>         else:
> -            # Update immediately.
>             update()
>
>     def push_tree(self, pn):

Better. But couldn't you remove the update function completely and
just inline the code in it, since it's called immediately?

-- 
Karl Wiberg, kha@treskal.com
   subrabbit.wordpress.com
   www.treskal.com/kalle

  reply	other threads:[~2009-12-19 23:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 23:22 [RFC PATCH] Record a single transaction for conflicting push operations Catalin Marinas
2009-12-18  9:23 ` Karl Wiberg
2009-12-18 15:49   ` Catalin Marinas
2009-12-19 23:50     ` Karl Wiberg [this message]
2009-12-20 23:21       ` Catalin Marinas
2009-12-21  7:08         ` Karl Wiberg
2009-12-21 11:48           ` Catalin Marinas
2009-12-21 13:48             ` Karl Wiberg
2009-12-21 14:31               ` Gustav Hållberg
2009-12-22 18:33               ` Catalin Marinas

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=b8197bcb0912191550u300a9c20o351eba66c85292bb@mail.gmail.com \
    --to=kha@treskal.com \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gustav@virtutech.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).