public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Alexander Holler <holler@ahsoftware.de>
Cc: richard -rw- weinberger <richard.weinberger@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: What is tip-bot?
Date: Tue, 19 Feb 2013 17:14:33 -0800	[thread overview]
Message-ID: <51242379.9030909@infradead.org> (raw)
In-Reply-To: <51241ED2.5080105@ahsoftware.de>

On 02/19/13 16:54, Alexander Holler wrote:
> Am 19.02.2013 23:54, schrieb Randy Dunlap:
>> On 02/19/2013 02:36 AM, Alexander Holler wrote:
>>> Am 19.02.2013 10:54, schrieb richard -rw- weinberger:
>>>> On Tue, Feb 19, 2013 at 10:40 AM, Alexander Holler
>>>> <holler@ahsoftware.de> wrote:
>>>>> Hello,
>>>>>
>>>>> until now I could successfully suppress my curiosity about those
>>>>> tip:foo
>>>>> messages, but as the bot (or one of them) has now catched me too, I
>>>>> want to
>>>>> ask what it is.
>>>>>
>>>>> Searching for "tip(-)bot" or similiar doesn't reveal some useful info
>>>>> (for
>>>>> obvious reasons). Could someone give me an URL to source or
>>>>> documentation
>>>>> about that tool so that I can enlight myself about it's meaning?
>>>>
>>>> AFAIK tip-bot is a set of shell scripts used by _T_glx, _I_ngo and
>>>> _P_eter. :)
>>>>
>>>
>>> So messages from tip-bot are just acknowledgments (like those from Greg)
>>> that a patch has found it's way into one of the trees, with the
>>> difference that tip-bot sends those acknowledgments to lkml too, whereas
>>> Greg's scripts send them only to involved parties and not the lkml?
>>
>> Yes, that is my understanding of it.
>>
> 
> Thanks a lot for clarification.
> 
> In the meanwhile I've found an article at lwn about the kernel development process which lists many of the git repositories used by various maintainers. And that list includes tip. ;)
> 
> So the reason for my ignorance was that I didn't know that tip is actually the name of a git repository used by the x86 maintainers.

I can understand that.

The kernel tree MAINTAINERS file says for X86:

X86 ARCHITECTURE (32-BIT AND 64-BIT)
M:	Thomas Gleixner <tglx@linutronix.de>
M:	Ingo Molnar <mingo@redhat.com>
M:	"H. Peter Anvin" <hpa@zytor.com>
M:	x86@kernel.org
T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/core
S:	Maintained
F:	Documentation/x86/
F:	arch/x86/



-- 
~Randy

      reply	other threads:[~2013-02-20  1:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19  9:40 What is tip-bot? Alexander Holler
2013-02-19  9:54 ` richard -rw- weinberger
2013-02-19 10:36   ` Alexander Holler
2013-02-19 22:54     ` Randy Dunlap
2013-02-20  0:54       ` Alexander Holler
2013-02-20  1:14         ` Randy Dunlap [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=51242379.9030909@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=holler@ahsoftware.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@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