[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [RRG] RRG process clarification

To: "'Lixia Zhang'" <lixia@CS.UCLA.EDU>, "'rrg'" <rrg@psg.com>
Subject: RE: [RRG] RRG process clarification
From: "Tony Li" <tony.li@tony.li>
Date: Fri, 2 May 2008 09:47:57 -0700
In-reply-to: <E74B4DD0-EF25-425D-96DE-3A0990339C49@CS.UCLA.EDU>
References: <E74B4DD0-EF25-425D-96DE-3A0990339C49@CS.UCLA.EDU>
Reply-to: <tony.li@tony.li>

 


|Does the above miss any other branches at the top level design tree?


It should be noted that some folks come at things with an alternate
branching structure:

	- Map-n-encap
	- Translation
	- Transport

Which branching structure to use is also open for discussion.

Regards,
Tony


--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg

Follow-Ups:
- Re: [RRG] RRG process clarification
  - From: Scott Brim <swb@employees.org>
- Re: [RRG] RRG process clarification
  - From: Lixia Zhang <lixia@CS.UCLA.EDU>

References:
- Re: [RRG] RRG process clarification
  - From: Lixia Zhang <lixia@CS.UCLA.EDU>

Prev by Date: RE: [RRG] RRG process clarification
Next by Date: RE: [RRG] RRG process clarification
Previous by thread: Re: [RRG] RRG process clarification
Next by thread: Re: [RRG] RRG process clarification
Index(es):
- Date
- Thread