Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Cedric Le Goater <legoater-GANU6spQydw@public.gmane.org>
Cc: Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 1/1] cr: uts: don't pass an unsigned var as a signed int
Date: Tue, 23 Jun 2009 08:05:22 -0500	[thread overview]
Message-ID: <20090623130522.GA17948@us.ibm.com> (raw)
In-Reply-To: <4A40BF4F.9080704-GANU6spQydw@public.gmane.org>

Quoting Cedric Le Goater (legoater-GANU6spQydw@public.gmane.org):
> > would it be possible to put up a filter, either manual or
> > automatic, to send every patch that gets pushed on the current
> > ckpt git branch to the containers list, maybe with a [CKPT PUSH]
> > tag in the subject line?
> 
> you might want to use the 'post-receive' hook  like it's done on lxc-devel@ :
> 
> http://sourceforge.net/mailarchive/forum.php?thread_name=E1MF7MN-00089i-Oz%40fxgxhf1.ch3.sourceforge.com&forum_name=lxc-devel
> 
> Cheers,
> 
> C.

Thanks, neat idea.

As Nathan pointed out, it would be better (in terms of assuring upstream
maintainers of quality of the tree) to demand an ack *before* pushing to
git.  But even so, a post-receive hook would still be nice.

-serge

  parent reply	other threads:[~2009-06-23 13:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 20:37 [PATCH 1/1] cr: uts: don't pass an unsigned var as a signed int Serge E. Hallyn
     [not found] ` <20090619203719.GA30093-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-06-20  4:27   ` Nathan Lynch
     [not found]     ` <m3prczfs2m.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-06-21  0:18       ` Serge E. Hallyn
     [not found]         ` <20090621001837.GA32394-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
2009-06-21  5:29           ` Nathan Lynch
     [not found]             ` <m34ouaf942.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-06-21 13:53               ` Serge E. Hallyn
2009-06-21 19:13               ` Serge E. Hallyn
     [not found]                 ` <20090621191305.GA2499-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
2009-06-22  4:13                   ` Nathan Lynch
     [not found]                     ` <m3fxdsc3dm.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-06-24 17:07                       ` Oren Laadan
2009-06-23 11:41                   ` Cedric Le Goater
     [not found]                     ` <4A40BF4F.9080704-GANU6spQydw@public.gmane.org>
2009-06-23 13:05                       ` Serge E. Hallyn [this message]
2009-06-22 23:20   ` Nathan Lynch

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=20090623130522.GA17948@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=legoater-GANU6spQydw@public.gmane.org \
    --cc=ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org \
    /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