On Wed, Dec 12, 2012 at 10:17 AM, Roy Stogner <royst...@ices.utexas.edu>wrote:
> The PECOS CI server actually is publicly accessible. It's so hammered
> right now that I'd rather not subject its interface to even more usage
> until we get some new hardware going, but email me privately if you
> want the URL to peek at occasionally.
>
Sounds good. Is there any way we could run a build bot "slave" (I don't
know the BuildBot parlance) here at INL that would report our test status
back to your Build Bot server? If so, we could definitely set that up.
Also, I have some libMesh changes that I'm going to be making today, so I
was thinking about my Git workflow a little bit. I think even _I_ am going
to clone the libMesh Git repo on GitHub over into my own workspace and work
on my own changes there and then submit a pull request when those changes
are ready. "Submit a pull request" is essentially akin to emailing a patch
so others can ok your work.
Now, if I submit a pull request and everyone is ok with it... I can do my
own pull into the officially libMesh git clone on my workstation and merge
to master and push on my own. I just like the idea of ok'ing my patches
with a pull request first. For small things, I might not do that (just
little bug fixes) but for anything adding or changing API I think it might
be a good idea.
Note though, that this is a personal decision that I don't expect everyone
to follow.
What do you guys think?
Derek
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
