FYI, here is a github nugget from the scipy people:
-------- Original Message --------
Subject: Re: [SciPy-Dev] Used "Automatic Merge" on my github pull
request...
Date: Sun, 22 May 2011 11:49:44 +0200
From: Ralf Gommers <ralf.gomm...@googlemail.com>
Reply-To: SciPy Developers List <scipy-...@scipy.org>
To: SciPy Developers List <scipy-...@scipy.org>
On Sun, May 22, 2011 at 7:51 AM, Warren Weckesser
<warren.weckes...@enthought.com <mailto:warren.weckes...@enthought.com>>
wrote:
I used the "Automatic merge" button on my own pull request on
github, but afterwards discovered that it uses --no-ff, so my single
commit also resulted in a "merge" commit:
https://github.com/scipy/scipy/commit/cf04a2b8dd4cf258413687ec146883ea5ab197cb
Should I try to get rid of that merge? If so, how? (The git book
is by my side, but I suspect an answer will show up here faster than
I can find it.)
No, it's public now so you shouldn't touch it anymore.
That button is very pointless - best to ignore it.
Ralf
_______________________________________________
SciPy-Dev mailing list
scipy-...@scipy.org
http://mail.scipy.org/mailman/listinfo/scipy-dev
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
