On 04/20/2017 12:54 PM, Pete Jemian wrote:
> On 4/13/2017 1:39 PM, Andrew Johnson wrote:
>> The Git URL to clone is https://git.launchpad.net/epics-base
>
> Is this the preferred location?
Yes. Make sure you're working on the correct branch if you're working on
a bug-fix, the master branch will become 3.16 when we release
Base-3.16.1 but we like to fix bugs in the earliest branch where they
appear and merge the fixes upwards.
We have recently migrated the EPICS Base source code from Bazaar to Git,
but we are sticking with Launchpad for hosting because of the large
collection of development branches, bug reports, merge requests and
history there. Launchpad doesn't yet integrate with Git quite as well as
it did with Bazaar, but it works well enough for our purposes. It does
allow us to track a bug's status separately on the different branches,
while Github's support for bug tracking is less comprehensive.
That said there is a mirror of the Base repository on Github at
https://github.com/epics-base/epics-base and if someone really doesn't
want to create an account on Launchpad just in order to create a merge
request there we will accept pull requests for Base through Github (or
you can send patch files from git to the core-talk list).
- Andrew
> On 4/20/2017 12:19 PM, Mark S. Engbretson wrote:
>> There are probably a LOT of people using Windows that, like I normally
>> do,
>> make changes or corrections to local copies of Epics configurations .
>> . . .
>> and then do it again and again and again on other systems when a fresh
>> deployment of everything is grabbed or someone uses a different
>> version of a
>> Microsoft compiler.
>>
>> Since Base is up on Github, would that be the preferred location to be
>> submit such changes? ('cause I would like expected and accepted warning
>> messages to go away as much as the next person.)
>>
>> -----Original Message-----
>> From: Johnson, Andrew N. [mailto:anj@aps.anl.gov]
>> Sent: Thursday, April 20, 2017 11:50 AM
>> To: Engbretson, Mark S. <engbretson@aps.anl.gov>; tech-talk@aps.anl.gov
>> Subject: Re: EPICS V4 Windows build warning messages.
>>
>> Hi Mark,
>>
>> On 04/19/2017 03:42 PM, Mark S. Engbretson wrote:
>>> Although shouldn't this solution be merged into Epics base so that it
>>> goes away for everyone in the future?
>>
>> Done (committed to the 3.14 branch from where it will get merged into the
>> other branches). Thanks for pushing for that.
>>
>>> The linux builds of much of the Epics code compiles clean. The window
>>> compilers . . . . not so much so.
>>
>> None of the core developers have much love of working on Windows, so
>> as an
>> EPICS platform it may be a somewhat neglected child. If someone with
>> suitable expertise wanted to help clean up the code-base I don't think we
>> would refuse any offers of help.
>>
>> - Andrew
>>
>> --
>> Arguing for surveillance because you have nothing to hide is no different
>> than making the claim, "I don't care about freedom of speech because I
>> have
>> nothing to say." -- Edward Snowdon
>>
>
--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon