[request-sponsor] [6368560] request sponsor

2007-12-18 Thread Jan Pechanec
On Wed, 12 Dec 2007, Mike Kupfer wrote:

>This bug is in code that Solaris gets from upstream developers.  The
>team that owns the code in Solaris has said that they would prefer that
>the fix happen upstream.  Solaris will get the fix the next time the
>team synchronizes with the upstream code.
>
>So I'm afraid this isn't really suitable for a fix through
>request-sponsor.

OpenSSH already incorporated the suggested fix so I just confirm 
that I'll resync the change the next time I'm touching SunSSH code.

J.

-- 
Jan Pechanec



[request-sponsor] [6368560] request sponsor

2007-12-13 Thread ashwin
Hello all

Here is the patch for the bug 6368560

Bug Description:
extra backslashes in RB_PROTOTYPE

The extra backslash on the last line of  RB_PROTOTYPE macro is removed
in file usr/src/cmd/ssh/include/sys-tree.h


I would like to request a sponsor to evaluate my work and help me get it
integrated into the next build.


My contributor agreement # is OS0144

Thank You in advance.

-- 
Regards
Ashwin Bhat K S
3 year information technology
NATIONAL INSTITUTE OF TECHNOLOGY KARNATAKA Surathkal
Sun campus ambassador
99644 98351

Here is the unified diff for the patch -


--- sys-tree.h.orig Thu Dec 13 00:40:51 2007
+++ sys-tree.h  Thu Dec 13 00:45:42 2007
@@ -385,7 +385,6 @@
 struct type *name##_RB_FIND(struct name *, struct type *); \
 struct type *name##_RB_NEXT(struct name *, struct type *); \
 struct type *name##_RB_MINMAX(struct name *, int); \
-   \

 /* Main rb operation.
  * Moves node close to the key of elm to top
-- next part --
A non-text attachment was scrubbed...
Name: diffextrabackslash
Type: application/octet-stream
Size: 369 bytes
Desc: not available
URL: 



[request-sponsor] [6368560] request sponsor

2007-12-12 Thread Mike Kupfer
> Here is the patch for the bug 6368560
> 
> Bug Description:
> extra backslashes in RB_PROTOTYPE

This bug is in code that Solaris gets from upstream developers.  The
team that owns the code in Solaris has said that they would prefer that
the fix happen upstream.  Solaris will get the fix the next time the
team synchronizes with the upstream code.

So I'm afraid this isn't really suitable for a fix through
request-sponsor.

sorry,
mike