All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky Project <poky@yoctoproject.org>
Subject: [OT] splitting GIT repositories
Date: Thu, 08 Sep 2011 06:55:12 -0600	[thread overview]
Message-ID: <4E68BB30.9070300@mlbassoc.com> (raw)

Sorry for the off-topic question, but I'm sure that I'm not the
only Poky user out there that has a similar dilemma.

When I started working with Poky (quite some years ago), I added
my code/recipes/... to the Poky GIT tree locally.  This let me
keep my parts up to date with the global repository fairly easily.
I've tried to keep things such that my changes are separated from
the Poky master changes.

Now that the layering system is working well, and indeed I could
move from pure Yocto/Poky to oe-core, I'd like to split my files
away from the Poky tree I've been using.  I'd also like to keep
history, etc, for my code as I do this.

Is there some way to purge Poky master from my local tree?  In
other words, remove all the Yocto/Poky files & directories, including
any history/commits/etc that go along with them?

I've experimented some with clone + filter-branch which does
strip away the parts I don't want, but the history is cluttered
with Poky mainline commits.  In the end, I'd like to end up with
just my files and the commits that created them.

Thanks for any pointers or ideas

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2011-09-08 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 12:55 Gary Thomas [this message]
2011-09-08 13:52 ` [OT] splitting GIT repositories Chris Larson
2011-09-08 13:58   ` Gary Thomas
2011-09-20 15:32     ` Gary Thomas

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=4E68BB30.9070300@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.