public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Attn Maintainers: git advise needed (how to fix messed up repo)
Date: Tue, 29 Nov 2011 21:51:52 +1100	[thread overview]
Message-ID: <4ED4B948.9010701@gmail.com> (raw)
In-Reply-To: <201111290036.59408.vapier@gentoo.org>

On 29/11/11 16:36, Mike Frysinger wrote:
> On Tuesday 29 November 2011 00:04:12 Graeme Russ wrote:
>> I think I need to do some reading up on 'rebase' versus 'merge' in git

[snip]

>>> then you'll have to do:
>>>        $ git checkout master
>>>        $ git rebase u-boot/master
>>>        $ git push --force <remote uri> master
>>
>> Hmm, I don't think this will, in and of itself, help - The duplicate
>> commits are all local to u-boot-x86/master (they are all x86 patches, not
>> u-boot patches) but I'll give it a go first...
> 
> rebase should automatically discard changesets that are empty/already applied.  
> if it doesn't, use the interactive flag:
> 	$ git rebase -i u-boot/master
> then delete any duplicate lines in the text file that pops up

Well, I had already done a git reset --hard back to a point where there
were no x86 patches applied since last pull anyway, so the rebase threw
them all out

I went back into patchwork and downloaded all the patches and git am'd them
all. I was tempted to fix up a few that broke the build and had to be fixed
with a little fixup patch but I decided that I had tempted fate enough
already :)

So it's all fixed - Thanks for your help

However, I still get:

error: refs/tags/2009.01-rc2 does not point to a valid object!

Regards,

Graeme

  reply	other threads:[~2011-11-29 10:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 22:31 [U-Boot] Attn Maintainers: git advise needed (how to fix messed up repo) Graeme Russ
2011-11-28 23:02 ` Mike Frysinger
2011-11-28 23:05   ` Graeme Russ
2011-11-28 23:13     ` Mike Frysinger
2011-11-28 23:16       ` Andy Fleming
2011-11-28 23:20         ` Graeme Russ
2011-11-28 23:43           ` Mike Frysinger
2011-11-29  0:02             ` Graeme Russ
2011-11-29  3:31               ` Mike Frysinger
2011-11-29  3:35                 ` Graeme Russ
2011-11-29  4:01                   ` Mike Frysinger
2011-11-29  4:17                     ` Graeme Russ
2011-11-29  4:49                       ` Mike Frysinger
2011-11-29  5:04                         ` Graeme Russ
2011-11-29  5:31                           ` Andy Fleming
2011-11-29  5:36                           ` Mike Frysinger
2011-11-29 10:51                             ` Graeme Russ [this message]
2011-11-29 15:08                               ` Mike Frysinger
2011-11-29 22:57                             ` Graeme Russ
2011-11-29 23:35                               ` Mike Frysinger
2011-11-29 23:48                                 ` Graeme Russ
2011-11-30  3:52                                   ` Mike Frysinger
2011-11-30  4:12                                     ` Graeme Russ
2011-11-30 16:41                                       ` Mike Frysinger
2011-11-29  9:55   ` Graeme Russ

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=4ED4B948.9010701@gmail.com \
    --to=graeme.russ@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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