rethinking patch management with GIT / topgit

[Petr Baudis]

On Sun, Mar 28, 2010 at 03:56:54PM -0700, Manoj Srivastava wrote:
> On Sun, Mar 28 2010, Petr Baudis wrote:
> 
> > My original motivation for TopGit development was that I actually was
> > the _only_ developer, but I needed to maintain and develop in multiple
> > clones in a sensible way.
> >
> > Maybe you are happy doing things your way, but I'm trying to explain why
> > many people aren't.
> 
>         I have no objection to people preferring different workflows than
>  the one I use, as long as they do not tell me that mine is irrelevant,
>  obsolete, or otherwise incorrect. (and I am missing the email that I
>  have commented on in the thread where you, and not Enrico, is
>  explaining their workflow, so I might be somewhat off base here).

  I'm sorry for the confusion, the second paragraph in my mail was not
meant at you but Enrico.

>         To come to your email, are you stating that TopGit is designed
>  for people working alone, or in small teams, and not publishing their
>  branches for other people to work on? If that is the case, it is
>  certainly a valid use case, but certainly not universal; and might not
>  be suited for a chain of repositories where several distribution
>  package maintainers derive from the work on their immediate upstream
>  distribution.

  No, I'm not saying that, I only stated my motivation. TopGit was
designed to provide universal support for distributed workflows.

-- 
				Petr "Pasky" Baudis
http://pasky.or.cz/ | "Ars longa, vita brevis." -- Hippocrates