On Tue, 2 Jul 2013 16:32:34 -0400
Ian McMahon wrote:
> Beautiful!
>
> On Jul 2, 2013, at 4:30 PM, Chris Radek wrote:
> > I had
> > not done this on ours, but I have now; thanks for the reminder.
See, the system does work, at least sometimes :)
Thanks,
Matt
-
Beautiful!
On Jul 2, 2013, at 4:30 PM, Chris Radek wrote:
> On Tue, Jul 02, 2013 at 02:20:41PM -0400, Ian McMahon wrote:
>>
>> One, and this may be pretty minor, but when you use github and
>> friends, it has a nice big "this is the git url to clone" at the
>> top of the page. Gitweb doesn't
On Tue, Jul 02, 2013 at 02:20:41PM -0400, Ian McMahon wrote:
>
> One, and this may be pretty minor, but when you use github and
> friends, it has a nice big "this is the git url to clone" at the
> top of the page. Gitweb doesn't, and it's not immediately obvious
> how to translate what's in gitwe
I've use both git and mercurial for various projects (as well as svn,
and cvs). I prefer mercurial because it has a lower learning curve, and
can do everything that git can do with a little more work. Basically
the day to day things are simple, and the huge things like merging
repositories ta
And three, github and friends are relatively easy to deal with in terms of key
management and authentication. I think I gave Michael an ssh key once upon a
time for my access to his repo, but I don't really remember, and if so, which
key?
On Jul 2, 2013, at 2:20 PM, Ian McMahon wrote:
>
> S
So, two comments on the topic:
One, and this may be pretty minor, but when you use github and friends, it has
a nice big "this is the git url to clone" at the top of the page. Gitweb
doesn't, and it's not immediately obvious how to translate what's in gitweb to
a clone url.
Two, if I want to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/2/2013 10:42 AM, Sebastian Kuzminsky wrote:
>
> 1:
> http://buildbot.linuxcnc.org/doc/scratch/v2.5.2~contributor-docs-1~f892e30/html/code/Contributing-to-LinuxCNC.html
Looks
>
great! One thing I would add is in step 3 where you say "Push
your
On 7/1/13 11:15 , Ian McMahon wrote:
>
> On Jul 1, 2013, at 11:45 AM, Matt Shaver wrote:
>
>> OK, I want to start making a "HOWTO Contribute To The Project" wiki
>> page. Linked to that page will be this page that's at least the
>> beginnings of what you want:
>> http://wiki.linuxcnc.org/cgi-bin/w
On Jul 1 2013 10:30 PM, Alec Ari wrote:
> I've converted several non-git projects to git projects simply
> because of how easy it is... Is CVS impossible or is it just me?
CVS is old enough and lacking in features that most people move to at
least SVN, if not Mercurial of GIT. So, CVS is better
I've converted several non-git projects to git projects simply because of how
easy it is... Is CVS impossible or is it just me?
Alec
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.ne
Matt Shaver wrote:
>
>
> I'm terrible with Git. At the CNC Workshop in Ann Arbor in 2011 (I
> think) Seb spent thousands of calories trying to educate me on Git and
> its ways and uses. It did some good, but I'm a long way from
> competency. It is however, _the tool_ for this type of work, and I (a
On Jul 1, 2013, at 11:45 AM, Matt Shaver wrote:
> This is, IMHO, _the_ argument FOR using github/bitbucket. My desire
> would be to replicate this functionality AND achieve similar results
> (efficiency, large number of reviewers, etc) within our current
> infrastructure at linuxcnc.org. If this
On Sun, 30 Jun 2013 13:15:55 -0400
Ian McMahon wrote:
> however it shakes out, there needs to be some clear direction on the
> best practices for managing development on branches and forks, how
> pull requests and merges should be done, who can and will review and
> merge them, etc.
I agree with
On Sun, 2013-06-30 at 12:28 -0400, Matt Shaver wrote:
> On Sat, 29 Jun 2013 18:15:54 -0500
> Charles Steinkuehler wrote:
>
> > So what do I think needs to change? Well, let's start with what
> > exists now, which I see as:
> >
> > Tier 1) Anointed LinuxCNC developers with push access to
> > git
however it shakes out, there needs to be some clear direction on the best
practices for managing development on branches and forks, how pull requests and
merges should be done, who can and will review and merge them, etc.
I'm heavily in favor of using a service like github or bitbucket because I
On Sat, 29 Jun 2013 18:15:54 -0500
Charles Steinkuehler wrote:
> So what do I think needs to change? Well, let's start with what
> exists now, which I see as:
>
> Tier 1) Anointed LinuxCNC developers with push access to
> git.linuxcnc.org.
<...>
> Tier 2) People who have pestered or persisted e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/29/2013 10:57 PM, Sebastian Kuzminsky wrote:
> This does not provide the kind of shared development space that we
> occasionally use (for example the rtos branch that Michael and
> Zultron and Charles worked on, or the halui jog test fix branch
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/29/2013 10:08 PM, Sebastian Kuzminsky wrote:
> On 06/29/2013 05:15 PM, Charles Steinkuehler wrote:
>>
>> Basically, I don't care what happens as long as it is clear (ie:
>> listed plainly wherever folks are pointed to git.linuxcnc.org to
>> grab
On 06/29/2013 09:06 PM, Matt Shaver wrote:
> On Sat, 29 Jun 2013 21:34:43 -0500
> Charles Steinkuehler wrote:
>
>> Anyway, what I really want is a way for Joe Average New User to be
>> able to tweak a HAL component, configuration, kinematics module, or
>> similar, share the results with the commun
On Sat, 29 Jun 2013 21:34:43 -0500
Charles Steinkuehler wrote:
> IMHO, there really needs to be a "Sid" branch of LinuxCNC that is
> GUARANTEED to break your machine and kill the machine operator (anyone
> in the field actually using this on real equipment deserves what they
> get!), but is used
On 06/29/2013 05:15 PM, Charles Steinkuehler wrote:
> Tier 3) Everyone else. It is currently difficult to "elegantly" share
> any updates with others. I can very easily clone git.linuxcnc.org to
> my box and make some changes, but then what? Do I post a patch to the
> mailing list (ignored and/o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/29/2013 9:06 PM, Chris Morley wrote:
>
> Well it seems we have a few options at the moment - even one I
> didn't know about.
>
> You could send a git patch to the mail list.
As mentioned, this tends to get lost/ignored.
> You can submit a patc
> Tier 3) Everyone else. It is currently difficult to "elegantly" share
> any updates with others. I can very easily clone git.linuxcnc.org to
> my box and make some changes, but then what? Do I post a patch to the
> mailing list (ignored and/or easily lost)? Do I open my local git
> repositor
>Does this sound reasonable?
Very!
>If so, what changes do we need to make it work?
None that I can think of..
Alec
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/window
On Saturday 29 June 2013 20:58:56 Charles Steinkuehler did opine:
> Per the IRC meeting this morning (my time), I'd like to discuss
> possible changes to the LinuxCNC git management.
>
> Let me start by saying I do not wish to do away with git.linuxcnc.org,
> nor do I have any particular desire t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Per the IRC meeting this morning (my time), I'd like to discuss
possible changes to the LinuxCNC git management.
Let me start by saying I do not wish to do away with git.linuxcnc.org,
nor do I have any particular desire to involve github in this whole
26 matches
Mail list logo
