search

sccn / SIFT

SIFT is an EEGLAB-compatible toolbox for analysis and visualization of multivariate causality and information flow between sources of electrophysiological (EEG/ECoG/MEG) activity. It consists of a suite of command-line functions with an integrated Graphical User Interface for easy access to multiple features. There are currently six modules: data preprocessing, model fitting and connectivity estimation, statistical analysis, visualization, group analysis, and neuronal data simulation.
https://sccn.ucsd.edu/wiki/SIFT
Other
31 stars 5 forks source link

Re-push the repository #5

Open tstenner opened 3 years ago

tstenner commented 3 years ago

Before this repository appeared on Github, I had converted the original Bitbucket mercurial repository to a git repository to track my changes internally (https://github.com/tstenner/sift). At some point or an other, some binaries that were later deleted have been committed accidentally, but they were still in the history taking up ~140MB, so I removed them with the BFG repo cleaner, basically checking out each commit, removing the binaries and rebasing the following history onto these commits. The repository contents (minus those binaries) are identical, but the commit hashes differ, so I can't push any PRs to this repository without creating patch files from my repository, applying them to a separate clone of this repository and then pushing them.

Therefore, I think it'd be a good idea to force push the contents of my repository to this one (including the 3 latest commits from the bitbucket repository).

arnodelorme commented 3 years ago

Would you mind to fork the current repo. Manually copy your changes and make a push request.

Cheers, Arno

On Apr 25, 2021, at 10:41 PM, Tristan Stenner @.***> wrote:

Before this repository appeared on Github, I had converted the original Bitbucket mercurial repository to a git repository to track my changes internally (https://github.com/tstenner/sift). At some point or an other, some binaries that were later deleted have been committed accidentally, but they were still in the history taking up ~140MB, so I removed them with the BFG repo cleaner, basically checking out each commit, removing the binaries and rebasing the following history onto these commits. The repository contents (minus those binaries) are identical, but the commit hashes differ, so I can't push any PRs to this repository without creating patch files from my repository, applying them to a separate clone of this repository and then pushing them.

Therefore, I think it'd be a good idea to force push the contents of my repository to this one (including the 3 latest commits from the bitbucket repository).

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

tstenner commented 3 years ago

I only have a shallow clone locally, but I'll hopefully get around to it in a few days. Meanwhile, I'll push PRs for Tim's latest commits and some of my own changes.