git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: Can I remove stg sync --undo ?
Date: Fri, 4 Jul 2008 23:05:11 +0100	[thread overview]
Message-ID: <b0943d9e0807041505oc15660bpcd62a62100e517b9@mail.gmail.com> (raw)
In-Reply-To: <20080704020918.GA30669@diana.vm.bytemark.co.uk>

2008/7/4 Karl Hasselström <kha@treskal.com>:
> On 2008-07-03 23:02:28 +0100, Catalin Marinas wrote:
>> The sync performs three operations - push, merge and refresh (if the
>> refresh is automatic after merge, it doesn't update the backup
>> information since it was done by merge).
>>
>> If merge fails, the refresh is manual after solving the conflicts. I
>> suspect this will be recorded as a separate step for undo
>
> Yeah, the new undo stuff will currently handle sync just like e.g.
> push and pop: write one log entry when the command's all done, plus
> one extra just before the conflicting push if there is one. So you can
> always undo the entire command; and in case of conflicts, you also
> have the option of undoing just the conflicting push. Is this enough
> for sync?

There are two operations that can conflict for sync - pushing a patch
and the actual sync'ing, i.e. a three-way merge with the patch to be
synchronised with (kind of fold).

>> (BTW, is resolved take into account for undo?).
>
> Hmmm, what do you mean by "resolved"?

The current resolved command - the clearing of the conflicting entries
in the index.

-- 
Catalin

  reply	other threads:[~2008-07-04 22:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02  7:25 Can I remove stg sync --undo ? Karl Hasselström
2008-07-03 22:02 ` Catalin Marinas
2008-07-04  2:09   ` Karl Hasselström
2008-07-04 22:05     ` Catalin Marinas [this message]
2008-07-05  8:33       ` Karl Hasselström
2008-07-07 20:47         ` Catalin Marinas
2008-07-08  4:14           ` 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=b0943d9e0807041505oc15660bpcd62a62100e517b9@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).