linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	linux-trace-devel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH 0/2] [RFC] several build fixes
Date: Tue, 6 Aug 2019 22:35:23 +0900	[thread overview]
Message-ID: <20190806133523.GA16932@tigerII.localdomain> (raw)
In-Reply-To: <20190806092702.31e62a83@gandalf.local.home>

On (08/06/19 09:27), Steven Rostedt wrote:
> > Hi,
> > 
> > 	RFC
> > 
> > These patches fix v1.1.1 build on my system.
> > 
> 
> Hi Sergey,
> 
> v1.1.1 is 8 years old and no longer supported.
> 
> Care to use the latest code? Otherwise, you'll need to simply maintain
> these changes locally.

Hi Steven,

Nah, was just some weird fault on my side. A very weird one. Never mind
those patches; I did git pull but it took 24h to realize that git pull
didn't work out and I was still looking at commits from 2011. I was like
"hold on a second, no way Steven would ever let this happen" and then I
checked the repository state... Which I cloned in 2011, yes.

My apologies!

	-ss

      reply	other threads:[~2019-08-06 13:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  5:59 [PATCH 0/2] [RFC] several build fixes Sergey Senozhatsky
2019-08-06  5:59 ` [PATCH 1/2] parse-event: rename filter_arg_boolean arg Sergey Senozhatsky
2019-08-06  5:59 ` [PATCH 2/2] makefile: fix python SyntaxError Sergey Senozhatsky
2019-08-06 13:27 ` [PATCH 0/2] [RFC] several build fixes Steven Rostedt
2019-08-06 13:35   ` Sergey Senozhatsky [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190806133523.GA16932@tigerII.localdomain \
    --to=sergey.senozhatsky@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).