On Thu, September 17, 2009 07:44, paul POULAIN wrote:
Daniel Grobani a écrit :
"We will not be making our git repo public as it contains
Just a short answer: That's a so poor, so illogic, so technically
irrelevant, and Josh is a so smart developer, that I simply can't
believe LL made it that way !
I can believe that people do many poorly conceived things when they are in
a hurry. I also know that Git is a very robust tool which can be used to
manage much more than source code data.
Yes, this is a main reason for the difficulty of republishing private
forks. Not only do you have to make sure that the git HEAD doesn't
contain confidential data that was added in error, but also that the
visible history doesn't show it.
git rebase -i => reorder your patches to put the offending patch on top
git reset --hard => remove it from your git tree
rm offendingfile.csv => remove the file definetly