From: Petr Baudis <pasky@ucw.cz>
To: git@vger.kernel.org
Subject: StGIT unhelpfulness
Date: Tue, 22 May 2007 13:16:03 +0200 [thread overview]
Message-ID: <20070522111603.GH4489@pasky.or.cz> (raw)
Hi,
I tried to stg pull to my git repository at repo.or.cz, but stg pull
only laconically announced
stg pull: Rebasing would possibly lose data
and left me with a confused stare. The same with popping all the patches
first, so there is actually nothing _to_ rebase, but it still fails.
Five minutes of peeking at the stgit code later, I think this is
because I sometimes do stg pull (now) and sometimes stg pop -a, cg
update, stg push -a when I'm feeling nostalgic. orig-base doesn't get
updated and stgit gets unhappy, but frankly, I don't even get _why_ does
it need to record and check orig-base - how does it matter?
Besides, when it doesn't like it, it should give me some more helpful
error message than just the cryptic above...
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Ever try. Ever fail. No matter. // Try again. Fail again. Fail better.
-- Samuel Beckett
next reply other threads:[~2007-05-22 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 11:16 Petr Baudis [this message]
2007-05-22 14:15 ` StGIT unhelpfulness Karl Hasselström
2007-05-22 14:18 ` 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=20070522111603.GH4489@pasky.or.cz \
--to=pasky@ucw.cz \
--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