On Wednesday, June 15, 2011 at 6:09 PM, Ian Ward Comfort wrote:
> On 15 Jun 2011, at 9:56 AM, Dan Bode wrote:
> > I just wanted to clarify something from this email. Although the best way
> > to get traction for a ticket in the future will be voting in the ticketing
> > system, people are alway
On 15 Jun 2011, at 9:56 AM, Dan Bode wrote:
> I just wanted to clarify something from this email. Although the best way to
> get traction for a ticket in the future will be voting in the ticketing
> system, people are always welcome to highlight particular tickets in order to
> solicit votes.
I
Just a heads-up that we won't have as much time to work on our normal
backlog & go through submitted patches over the next week or so due to
several of us being out for conferences and other travel obligations.
Finished backlog items:
* #4416 - Resources cannot be used on the run where they are
It looks like I was to restrictive here, see comments below
On Sat, Apr 23, 2011 at 11:16:34AM +0200, Stefan Schulte wrote:
> Whitespaces in any of the properties can lead to incorrect entries in
> the authorized_keys file.
>
> Signed-off-by: Stefan Schulte
> ---
> lib/puppet/type/ssh_authorize
Hi,
I just wanted to clarify something from this email. Although the best way to
get traction for a ticket in the future will be voting in the ticketing
system, people are always welcome to highlight particular tickets in order
to solicit votes.
With that in mind, a quick list of things that I ha
On 06/15/2011 09:11 AM, R.I.Pienaar wrote:
Below is a edit taking your 66 line changelog down to a usable 25 lines
by removing all the purely testing related lines, the merge lines and maint
lines.
I think this is already a huge improvement. Changelogs are what users use
to determine the suita
+1, well said :)
On 15.06.2011 10:11, R.I.Pienaar wrote:
I have a feature request for your announce mails :)
git log doesnt make a changelog, it makes a developer orientated
log of events in a git repository.
This information isnt aimed at users. A proper changelog highlighting
changes would
I have a feature request for your announce mails :)
git log doesnt make a changelog, it makes a developer orientated
log of events in a git repository.
This information isnt aimed at users. A proper changelog highlighting
changes would be a really good improvement. Even just stripping out the
n
