This is a great idea!
I wonder if my recent PR on licences skewed my result (in which I touched
nearly every file...).
Perhaps this should be an (automatically updating) example in the
scikit-learn gallery?
(that said, it could also be a good conference paper for you)
On 26 September 2013 03:31
Thanks Emanuele!
*Luca Cerone*
Tel: +447585611951
Skype: luca.cerone
On 27 September 2013 12:59, Emanuele Olivetti wrote:
> Hi,
>
> Fetching just retrieve the changes to your local copy of the remote
> branch, wihtout merging. Pull = fetch + merge.
> If you do as Gilles explained then you nee
Hi,
Fetching just retrieve the changes to your local copy of the remote
branch, wihtout merging. Pull = fetch + merge.
If you do as Gilles explained then you need to pull (or even better, to fetch
and
rebase) from refs/pull/2120/head:mlp whenever you want to use the latest changes
in PR #2120.
Suppose there is a sequence of observations. for an example take
[1,2,3,5,5,5,2,3,2,3, ..., 3, 4]. (Those can be even real numbers). How do
I use the current implementation of HMM in Scikit-learn to predict the next
value of this observation sequence. I have 2 questions regarding this.
1. Given a
Hi Gilles,
thanks for the quick reply :)
I just have one doubt, say that I find a bug in the pull request branch and
I fix it locally,
the second git fetch (upstream should be origin in our example, right?)
would behave as a normal pull,
merging what can be merged and asking to resolve eventual co
Hi Luca,
Let "origin" be the scikit-learn remote repo. From you local master branch
you did something like:
git fetch origin refs/pull/2120/head:mlp
which fetched PR #2120 into a local branch called "mlp".
If you want to retrieve the last commits of that PR, this is very simple.
You simply have
2013/9/27 Luca Cerone :
> For example, Issam explained me how to checkout his branch, which I did,
> but I can't understand now how to fetch eventual changes made to this
> branch.
>
> Is there a way to do this? On github I have found this help page:
> https://help.github.com/articles/checking-out
Hi everybody,
don't know if this is slightly off topic, in that case I apologize in
advance.
I would like to fetch and track a few pull requests (e.g. the multilayer
perceptron branch).
For example, Issam explained me how to checkout his branch, which I did,
but I can't understand now how to fet
I am quite busy until Monday (included) but I'll work after that on
the 1-page abstract. This shouldn't take very long. Also, I don't
think we need the demo to be ready by the time of submission, so this
leaves us even more time to prepare nice examples.
What do you think of the following structur
