Re: Git mirrors

[Eli Zaretskii]

> From: "Stephen J. Turnbull" <address@hidden>
> Cc: address@hidden,
>     address@hidden,
>     address@hidden,
>     address@hidden
> Date: Mon, 17 Oct 2011 20:57:51 +0900
> 
>  > Try disregarding its obvious exaggeration and disgust, and just _read_
>  > the portions of the man pages reproduced there.
> 
> Sure (I don't need to, I've read them myself), but that's almost
> irrelevant to introducing such a tool into the general workflow of a
> project.

I didn't say it was relevant.  I was just reflecting on documentation
quality, separately from the rest of this thread.

>  > [git people having trouble adjusting to bzr] could well be out of
>  > habit, though.
> 
> It is most definitely not habit in my case.  It's lack of colocated
> branches, and lack of technical documentation for pipelines and looms.
> I need technical documentation because I have a very clear idea of
> what workflows I want to implement, and the use cases and tutorials
> published for those tools don't match my workflow.

That's still "habit" from my POV: you are used to certain workflows,
and bzr doesn't lend itself easily to those workflows.  Same happens
to me in git: I _want_ to have separate branches, but git forces me to
have a separate repo for each branch, if I insist on that workflow...