From: Mike Frysinger <vapier@gentoo.org>
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 00:36:58 -0500 [thread overview]
Message-ID: <201111290036.59408.vapier@gentoo.org> (raw)
In-Reply-To: <CALButCJ4nB_uMNezAeMzOG0ToseBLAspTMMpGZNgGjdJJLsVLw@mail.gmail.com>
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
rebase: rewrites the history by taking all of your local changes and placing
them on top of the commit you've specified. this ultimately produces a much
more linear and "clean" history for people to review, but can lose information
(the exact code base a patch was written against) and be hard to work with
downstream.
merge: stitches together two related trees that have diverged. adds a "merge
commit" to the point where the two histories get stitched together. things
are not linear at all :).
> So then the question becomes - what about developers doing x86 work - I
> may have patches published in u-boot-x86/master which have not been pulled
> by Wolfgang, but u-boot/master may also contain patches that are needed
if that's the case, then i think doing a merge with Wolfgang's is acceptable
if you don't just want to have Wolfgang pull your tree as is
> Can you merge a local repo with multiple remotes? So could developer 'x':
certainly. that's the great thing about git -- every single git repo is on
"equal" footing in terms of what can be done regardless of who it is (you, me,
Wolfgang, random-person-who-has-never-posted-to-the-u-boot-list). the *only*
thing preventing changes being published on denx.de are ssh credentials.
> > 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
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20111129/58aec911/attachment.pgp>
next prev parent reply other threads:[~2011-11-29 5:36 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 [this message]
2011-11-29 10:51 ` Graeme Russ
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=201111290036.59408.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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