Agreed, changing the commit ancestry history of a branch that other people have
already (even merely potentially) fetched and checked out locally is generally
frowned upon. Interesting to hear that anyone ever has gotten consensus to do
so via "pull --rebase"! On rare occasions at my job we ha
On Tuesday, January 12, 2016 1:42 AM, Luc Maisonobe wrote:
Le 11/01/2016 23:11, Phil Steitz a écrit :> Now and then I want to go back and
research how the code got to be> the way it is. I used to be able to just jump
into the old> svn-viewc thingy. That is now blocked with a message that j
rebasing
as a tool to keep in mind, even if you don't employ it in this use case.
http://ProGit.org/book is a great, easy to read resource.
Al
From:"Luc Maisonobe"
Date:Sun, Sep 13, 2015 at 4:26
Subject:Re: [Math] Compile only top-level package and below
Hi Al,
Le 13/09/2015
You could use `git cherry-pick` to bring one or more commits from one branch
into another.
Al
There are several ways one could address this situation; I think I would simply
create a new branch in Git and commit those new files only on that branch.
Al
response.
Andreas has read this thread thus far and plans to join this mailing list.
Al
- Forwarded Message
> From: Andreas Rummler
> To: [EMAIL PROTECTED]
> Sent: Tuesday, April 1, 2008 12:56:52 AM
> Subject: Re: Fw: [math] Genetic Algorithms
>
> Al Chou schr
- Original Message
> From: Phil Steitz <[EMAIL PROTECTED]>
> To: Jakarta Commons Developers List
> Sent: Saturday, March 29, 2008 5:53:47 PM
> Subject: [math] Genetic Algorithms
>
> I would like to start work on a GA framework. This has been on the
> WishList for some time and I now hav
Not having ever looked at our FFT code, I won't address the issue of whether
the documentation is right or wrong (I suspect the documentation simply has a
typo; base-2 FFT's are the easiest to implement, given that they're the only
kind anyone ever seems to write about, so I can't believe we hav
