linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: master branch reset
Date: Tue, 5 Dec 2006 10:23:37 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.62.0612051022470.20543@pademelon.sonytel.be> (raw)
In-Reply-To: <528646bc0612050015xa18b33bh4afdc2f9d196f1a1@mail.gmail.com>

On Tue, 5 Dec 2006, Grant Likely wrote:
> On 12/5/06, Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> wrote:
> > On Tue, 5 Dec 2006, Grant Likely wrote:
> > > On 12/5/06, Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> wrote:
> > > > On Mon, 4 Dec 2006, Paul Mackerras wrote:
> > >
> > > > Any clues? Delete and reclone?
> > >
> > > Because Paul had to redo his tree; you're no longer able to 'pull' his
> > > changes into your branch.  If you've got changes that you need to
> > > preserve; then you need to either generate a diff between Paul's old
> > > HEAD and your HEAD; then apply that to a new branch based of Paul's
> > > new HEAD.
> > >
> > > Or; you can create a new branch based on the new HEAD and
> > > 'git-cherry-pick' your changes into it.
> > >
> > > Either way, it can be rather painful.
> > 
> > I didn't make any local changes, so I assumed I could just follow Paul's
> > instructions. But they failed.
> 
> You're in easy street then; assuming you just cloned from powerpc.git, just
> do:
> 
> git-reset --hard origin
> 
> and your done.

Apparently not :-(

| pademelon$ git-reset --hard origin
| pademelon$ git pull -v
| Unpacking 10843 objects
|  100% (10843/10843) done
| * committish: ef6a3165e75c189da82c943a081cd1da52068738
|   branch 'for-2.6.20' of git://www.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc
| * refs/heads/for-2.6.20: same as branch 'for-2.6.20' of git://www.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc
| * committish: e62438630ca37539c8cc1553710bbfaa3cf960a7
|   branch 'master' of git://www.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc
| * refs/heads/origin: does not fast forward to branch 'master' of git://www.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc;
|   not updating.
| pademelon$

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- Sony Network and Software Technology Center Europe (NSCE)
Geert.Uytterhoeven@sonycom.com ------- The Corporate Village, Da Vincilaan 7-D1
Voice +32-2-7008453 Fax +32-2-7008622 ---------------- B-1935 Zaventem, Belgium

  reply	other threads:[~2006-12-05  9:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 11:44 master branch reset Paul Mackerras
2006-12-05  7:41 ` Geert Uytterhoeven
2006-12-05  7:49   ` Grant Likely
2006-12-05  8:02     ` Geert Uytterhoeven
2006-12-05  8:15       ` Grant Likely
2006-12-05  9:23         ` Geert Uytterhoeven [this message]
2006-12-05 10:13           ` Sylvain Munaut
2006-12-05 10:58             ` Geert Uytterhoeven
2006-12-05 12:34               ` Andreas Schwab
2006-12-05 10:54           ` Andreas Schwab

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=Pine.LNX.4.62.0612051022470.20543@pademelon.sonytel.be \
    --to=geert.uytterhoeven@sonycom.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).