This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=12bd7c01cac39996f7b4a481bb476b141bf46149
The branch
On Mon, Jun 23, 2008 at 05:44:57PM +0200, Louis Rilling wrote:
> make_item()
> new_item = kmalloc();
> config_item_init_type_long_name();
> return new_item;
>
> drop_item(item)
> config_item_put(item);
> kfree(item);
This is never, ever safe. Consider that s
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=634f4f53b00c2c1ee49e02773e44d3352043f1c3
The tag, c
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=a174220359c48ad23e7474f71e40bfc5fedd3906
The tag, f
On Mon, Jun 23, 2008 at 07:02:15PM +0200, Rafael J. Wysocki wrote:
> On Monday, 23 of June 2008, Bob Peterson wrote:
> > > Yup, the patch in your Bugzilla is for code that is new in 2.6.26.
> > >
> > > Can you push your patch for inclusion into 2.6.26 so that 2.6.26 won't
> > > get released with
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=a193e83fa55d43c3216ac64d28252a9c2cf2b5ae
The branch
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=534045c7da331333e5389c4f25356931bebb583e
The branch
It seems there's been some confusion about what the config system (ccs
replacement) should be and do in cluster3. There were just two ideas I
offered way back at the beginning:
1. Move the update mechanism outside the config system.
2. What remains is the part that reads the local cluster.conf f
> Yup, the patch in your Bugzilla is for code that is new in 2.6.26.
>
> Can you push your patch for inclusion into 2.6.26 so that 2.6.26 won't
> get released with this regression?
>
> Thanks
> Adrian
Hi Adrian,
Unfortunately, I cannot. All access to the gfs2 "-nmw" git tree is
controlled by
On Mon, Jun 23, 2008 at 09:40:39AM -0500, Bob Peterson wrote:
> On Sun, 2008-06-22 at 12:09 +0300, Adrian Bunk wrote:
> > On Sat, Jun 14, 2008 at 10:12:03PM +0200, Rafael J. Wysocki wrote:
> > > This message has been generated automatically as a part of a report
> > > of recent regressions.
> > >
On Sun, 2008-06-22 at 12:09 +0300, Adrian Bunk wrote:
> On Sat, Jun 14, 2008 at 10:12:03PM +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=a2f1025d6e1595475afcdcd68d6f8205ecf99412
The branch
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".
http://sources.redhat.com/git/gitweb.cgi?p=cluster.git;a=commitdiff;h=0b8bd69b8f6a393958229551396057ac44ca5391
The branch
13 matches
Mail list logo
