welcome james

Hey folks,
 We just added james bowes to the set of folks who can
commit to the cvs
tree. James has submitted a metric boatload of patches to
yum (most of
them work, too) and so it seemed that to make him stop
bothering us with
patch requests it was just easier to give him check in
access. :-D

-sv


_______________________________________________
Yum-devel mailing list
Yum-devellinux.duke.edu
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel

seth vidal wrote:
> Hey folks,
>  We just added james bowes to the set of folks who can
commit to the cvs
> tree. James has submitted a metric boatload of patches
to yum (most of
> them work, too) and so it seemed that to make him stop
bothering us with
> patch requests it was just easier to give him check in
access. :-D
> 

I just made some checkins tonight for some of my outstanding
patches. 
Hopefully I did everything correctly (my CVS skills are a
little rusty); 
  please let me know if I didn't.

-James

> -sv
> 
_______________________________________________
Yum-devel mailing list
Yum-devellinux.duke.edu
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel

On Wed, 2006-11-22 at 21:38 -0500, James Bowes wrote:
> 
> seth vidal wrote:
> > Hey folks,
> >  We just added james bowes to the set of folks who
can commit to the cvs
> > tree. James has submitted a metric boatload of
patches to yum (most of
> > them work, too) and so it seemed that to make him
stop bothering us with
> > patch requests it was just easier to give him
check in access. :-D
> > 
> 
> I just made some checkins tonight for some of my
outstanding patches. 
> Hopefully I did everything correctly (my CVS skills are
a little rusty); 
>   please let me know if I didn't.
> 

for any of those that didn't break API it would be good to
merge to
3.0.X branch, too.

-sv


_______________________________________________
Yum-devel mailing list
Yum-devellinux.duke.edu
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel