On Mon, Jan 06, 2014 at 03:00:44PM -0500, Steven Rostedt wrote:
> On Mon, 6 Jan 2014 14:54:50 -0500
> Steven Rostedt wrote:
> >
> > Yeah, I screwed up.
> >
> > This should have been 2.3 and I screwed up the tags here :-/
> >
> > I'll try to fix things up.
> >
>
> I blame too much eggnog over
On Mon, 6 Jan 2014 14:54:50 -0500
Steven Rostedt wrote:
>
> Yeah, I screwed up.
>
> This should have been 2.3 and I screwed up the tags here :-/
>
> I'll try to fix things up.
>
I blame too much eggnog over the holiday break. I think I fixed things
up.
Thanks!
-- Steve
--
To unsubscribe fro
On Mon, 6 Jan 2014 13:36:52 -0600
Seth Forshee wrote:
> There is something odd about the updates you pushed though. You've now
> got a version 2.2.1 on your trace-cmd-stable-v2.2 branch, which used to
> be tagged trace-cmd-v2.2.1, and another 2.2.1 on master which now has
> that tag. I'm guessing
On Mon, Jan 06, 2014 at 02:07:53PM -0500, Steven Rostedt wrote:
> On Mon, 6 Jan 2014 11:56:24 -0600
> Seth Forshee wrote:
>
> > Hi Steve,
> >
> > Here's another patch for trace-cmd that I'm using in Debian. Please
> > consider it for your tree.
> >
> > It also looks like you haven't applied th
On Mon, 6 Jan 2014 11:56:24 -0600
Seth Forshee wrote:
> Hi Steve,
>
> Here's another patch for trace-cmd that I'm using in Debian. Please
> consider it for your tree.
>
> It also looks like you haven't applied the patches I sent a few months
> back [1][2]. I'm guessing you just forgot about th
Hi Steve,
Here's another patch for trace-cmd that I'm using in Debian. Please
consider it for your tree.
It also looks like you haven't applied the patches I sent a few months
back [1][2]. I'm guessing you just forgot about them, but please let me
know if there's something I need to fix. I also p
6 matches
Mail list logo
