[...]
>
> I guess if we can filter out merge commits and only show the real commit
> information it should be good?
>
> (See other message with individual commit messages)
Yeah, IMO git gives us lots of un-needed merge messages, not much more
we can really say other than merged master into branch,
On 12-02-26 11:20 PM, Frank Lanitz wrote:
Hi folks,
Just something I thought on last merges based on Jiri's patches. Its
hard to understand what this merges do just by reading the commit
message. Given, that we want to create the ChangeLog based on git log it
will be nearly impossible to create
On 12-02-26 11:20 PM, Frank Lanitz wrote:
Hi folks,
Just something I thought on last merges based on Jiri's patches. Its
hard to understand what this merges do just by reading the commit
message. Given, that we want to create the ChangeLog based on git log it
will be nearly impossible to create
Hi folks,
Just something I thought on last merges based on Jiri's patches. Its
hard to understand what this merges do just by reading the commit
message. Given, that we want to create the ChangeLog based on git log it
will be nearly impossible to create a good ChangeLog/Newsfile if we
don't keep c
Hi,
The commit here bumps the API and ABI and renames a signal. Just an FYI
for any plugin developers, though a quick grep shows only the GProject
plugin being affected in the Geany-Plugins project.
Cheers,
Matthew Brush
On 12-02-26 08:50 PM, Matthew Brush wrote:
Branch: refs/heads/mas
[...]
>> My personal preference would be some shared static function that any plugin
>> using markers could access.
>
> A simple ui_utils function to find and return the first available
> marker based on SC_MARK_AVAILABLE would suffice.
>
The absolute minimum we need is for Geany to set unused mar
Am 26.02.2012 02:05, schrieb Matthew Brush:
> On 12-02-25 04:29 PM, Michael Hall wrote:
>>
>> On 02/25/2012 06:00 PM, Colomban Wendling wrote:
>
>>> 2) Is this a general-purpose change or a patch that only should be in
>>> Ubuntu? I mean, I don't know of any other distribution using Unity so
>>> I
On Sun, 26 Feb 2012 13:08:14 +
WILLIAM FRASER wrote:
> There is a problem as I understand it with checking for the
> SC_MARK_AVAILABLE marker to see if a marker is available...
>
> Markers seem by default to be set to 0 (SC_MARK_CIRCLE) by scintilla.
"By default, all 32 markers are set to S
There is a problem as I understand it with checking for the
SC_MARK_AVAILABLE marker to see if a marker is available...
Markers seem by default to be set to 0 (SC_MARK_CIRCLE) by scintilla. So
there is no way to tell if a marker is being used with the default marker
icon (SC_MARK_CIRCLE), or is no
