git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: catalin.marinas@gmail.com
Cc: git@vger.kernel.org
Subject: "stgit rebase" should check for errors before changing tree
Date: Tue, 5 Jun 2007 20:59:40 +0400	[thread overview]
Message-ID: <200706052059.51173.arvidjaar@mail.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

{pts/0}% stg rebase 2.6.22-rc4
Checking for changes in the working directory... done
Popping all applied patches... done
Rebasing to "2.6.22-rc4"...
stg rebase: Unknown revision: 2.6.22-rc4^{commit}

well, now user is forced to reapply (push) all patches by hand, "stg rebase" 
lost history and state. It probably should check before popping patches.

stgit-0.12.1

-andrey

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2007-06-05 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 16:59 Andrey Borzenkov [this message]
2007-06-06 21:47 ` "stgit rebase" should check for errors before changing tree Yann Dirson

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=200706052059.51173.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    /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).