From: randy_dunlap <rdunlap@xenotime.net>
Date: Sat, 16 Jul 2005 04:39:22 GMT
Subject: Re: [PATCH] Documentation: update recommended workflow when working with others.
Message-ID: <20050715213922.66414ac5.rdunlap@xenotime.net>
In-Reply-To: <7vslyfo143.fsf@assigned-by-dhcp.cox.net>

On Fri, 15 Jul 2005 20:56:12 -0700 Junio C Hamano wrote:

> Clarify that the hierarchy implied by the recommended workflow
> is only informal.
> 
> Refer readers to nice illustration by Rundy Dunlap.
                                        Randy            (please)

> 
> Separate out the step to "push" to own public repository in the
> workflow.
> 
> Signed-off-by: Junio C Hamano <junkio@cox.net>
> ---
> 
>  Documentation/tutorial.txt |   65 ++++++++++++++++++++++++++++++--------------
>  1 files changed, 44 insertions(+), 21 deletions(-)
> 
> 70a7f8c18de2006a500059f3cb23d353250d0a9d
> diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
> --- a/Documentation/tutorial.txt
> +++ b/Documentation/tutorial.txt
> @@ -967,7 +967,19 @@ unpacked in the destination, unless rsyn
>  	Working with Others
>  	-------------------
>  
> -A recommended work cycle for a "project lead" is like this:
> +Although git is a truly distributed system, it is often
> +convenient to organize your project with an informal hierarchy
> +of developers.  Linux kernel development is run this way.  There
> +is a nice illustration (page 17, "Merges to Mainline") in Rundy
> +Dunlap's presentation (http://tinyurl.com/a2jdg).

and again.  :)

Thanks,
---
~Randy