I've written above about another solution (make 2 git repos, every one
based on the current one), so commit history for every ebuild/eclass
is preserved (in fact it's preserved for deleted files, but it's less
comfortable/common to access - you need to know such a file/dir was
there). Downside:
Can live without history. (especially my stupid EPIC mistakes)
2011/9/25 Sławomir Nizio slawomir.ni...@sabayon.org:
I've written above about another solution (make 2 git repos, every one
based on the current one), so commit history for every ebuild/eclass
is preserved (in fact it's preserved
I want history to be preserved.
Thanks.
--
Fabio Erculiani
I guess its cp then git rm then :)
Lets just start it, enough chit chat.
On 25 September 2011 13:35, Fabio Erculiani lx...@sabayon.org wrote:
I want history to be preserved.
Thanks.
--
Fabio Erculiani
On Sun, Sep 25, 2011 at 5:39 PM, Ian Whyman v00...@v00d00.net wrote:
I guess its cp then git rm then :)
Lets just start it, enough chit chat.
Right!
Feel free to go ahead
--
Fabio Erculiani
Yeah that is my home server pushing a backup of my sabayon git repos
to github... eheheh
--
Fabio Erculiani
Let me quickly introduce my simple idea.
(tl;dr: create copy of current overlay, remove Sabayon-only stuff from
it, then using some wizardy make the second overlay.)
I create a temporary throw-away git repository. It will be a copy of
current 'sabayon' overlay.
From it all Sabayon-only stuff
