From: Jean-Christian de Rivaz <jc@eclis.ch>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: I used git pull instead of stg pull !
Date: Tue, 10 Jul 2007 16:20:08 +0200 [thread overview]
Message-ID: <46939598.9000103@eclis.ch> (raw)
In-Reply-To: <20070710132957.GA9297@diana.vm.bytemark.co.uk>
Thanks a lot Karl,
Your method solved the problem perfectly.
Have a good day,
--
Jean-Christian de Rivaz
Karl Hasselström a écrit :
> On 2007-07-10 11:52:47 +0200, Jean-Christian de Rivaz wrote:
>
>> I have made the error to use the "git pull" command instead of the
>> "stg pull" command. The "git pull" have been executed successfuly,
>> but now stg seem to be confused:
>>
>> stg pull -n
>> stg pull: local changes in the tree. Use "refresh" to commit them
>>
>> stg new dummy -m "dummy"
>> stg new: HEAD and top are not the same. You probably committed
>> changes to the tree outside of StGIT. If you know what you
>> are doing, use the "refresh -f" command
>>
>> How can I restore the archive to a normal state for stg ?
>
> The problem is that you have committed a merge on top of the StGIT
> stack, and StGIT can't deal with that. You can undo the merge
> (provided that you haven't committed anything else on top of it) with
> "git reset --hard HEAD^".
>
> NOTE: "reset --hard" will erase uncommitted modifications to working
> tree files, so first make sure that "git status" doesn't report any
> modifications you want to keep.
>
> If you want to get a better view of what it is you're doing, you could
> fire up gitk and find the sha1 of the commit that is supposed to be at
> the top of the StGIT stack, and "git reset <sha1>" to that commit.
>
> Once the merge is undone, just "stg pull" like you wanted to do in the
> first place.
>
prev parent reply other threads:[~2007-07-10 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 9:52 I used git pull instead of stg pull ! Jean-Christian de Rivaz
2007-07-10 13:29 ` Karl Hasselström
2007-07-10 14:20 ` Jean-Christian de Rivaz [this message]
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=46939598.9000103@eclis.ch \
--to=jc@eclis.ch \
--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).