I think those of use new to git and multiply impaired (using Windows,
old) would find it helpful if somebody could explicitly lay out all the
steps in this workflow.
Chris
On 04/03/2013 20:49, Geoffrey Hutchison wrote:
Someone (Geoff, I assume) will need to give you permissions to use that
Hi Chris,
It seems that the core devs have direct commit access to the repo.
This means that you can essentially keep working as before.
1. Create an a/c at github.com and send the name to Geoff to add to
the Open Babel project (note: only applies to core devs I guess)
2. Install TortoiseGit
Just checking: I'm guessing the plan is to stick with (at least for now) the
tickets tracker at sourceforge, or move to the issue tracker at github?
And, less relevant to the GitHub Migration topic but still useful to know: is
the best way to drum up interest in fixing a bug to post to this
On Thu, Feb 28, 2013 at 6:16 PM, Geoffrey Hutchison geo...@pitt.edu wrote:
If you'd like to access and/or write changes, you'll need to use GitHub.
Hurray! What is the workflow for submitting a patch to github? Will the SVN
committers have write access to openbabel/openbabel, or should we fork
On 2013-03-01 00:16, Geoffrey Hutchison wrote:
Noel pointed out to me that the migration to the new SourceForge tracker,
etc. did weird things to SVN. That is, the SourceForge code browser points at
the migrated SVN, but the old SVN repository still exists. And all of us
have been using it.
On Fri, Mar 1, 2013 at 2:17 AM, David van der Spoel sp...@xray.bmc.uu.sewrote:
So how does one (re)gain access to git other than anonymous
git clone g...@github.com:openbabel/openbabel.git
I'm getting
Permission denied (publickey).
Someone (Geoff, I assume) will need to give you
On Fri, Mar 1, 2013 at 4:52 PM, David Lonie david.lo...@kitware.com wrote:
On Fri, Mar 1, 2013 at 2:17 AM, David van der Spoel sp...@xray.bmc.uu.se
wrote:
So how does one (re)gain access to git other than anonymous
git clone g...@github.com:openbabel/openbabel.git
I'm getting
Permission
Noel pointed out to me that the migration to the new SourceForge tracker,
etc. did weird things to SVN. That is, the SourceForge code browser points at
the migrated SVN, but the old SVN repository still exists. And all of us have
been using it.
One thing I've found is that each project has a
