subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan Corveleyn <>
Subject Re: Tip of the day: Cheatsheet for common cmdline client operations
Date Fri, 25 Aug 2017 11:03:58 GMT
[ cc -= svnbook-dev, as I guess this will not become book-material.
More below ... ]

On Thu, Jul 13, 2017 at 6:34 PM, C. Michael Pilato
<> wrote:
> On Thu, Jul 13, 2017 at 11:21 AM, Daniel Shahaf <>
> wrote:
>> [moving from users@ ]
>> Daniel Shahaf wrote on Fri, 30 Jun 2017 09:15 +0000:
>> > I just ran into the following cheatsheet:
>> >
>> >
>> >
>> > It covers the normal multi-user workflow, branching, etc..
>> >
>> > (Kudos to the author, Giorgio Signorini, not to me.)
>> As some of you know, the author gave us permission to incorporate that
>> cheatsheet into the official documentation.  Any volunteers to start the
>> process?
>> Cheers,
>> Daniel
> With respect to the author and the work he's done, I'm not really interested
> in us maintaining yet another collection of the same information already
> covered -- in some cases multiple times, when you factor in the reference
> sections -- by the book.  At best this cheatsheet would be an appendix.  I'm
> happy to link to the cheatsheet from from the book website, though.
> -- Mike

FWIW, I think this cheatsheet is quite good and valuable (though I
agree there is a lot of overlap with existing documentation),
especially for newcomers. Just to have a good summary / reminder of
common things you'll encounter.

We have our own quickstart page:

How about:

- Putting a link at the bottom of that page (there is already a link
to the quickstart section of the book), linking to the original
webpage of the author.


- Incorporating (some of) the content of that cheatsheet directly on, so it's right there in front
of you ...

The latter option would be my personal preference (putting my user /
admin hat on) -- I like having short info right in front of me in the
right place -- but obviously imposes some amount of doc-maintenance
work on "us".

Maybe someone on this list would be willing to take this doc-task
(migrating the current content, and keep an eye on keeping it up to


View raw message