[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Tip of the day: Cheatsheet for common cmdline client operations

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Thu, 21 Sep 2017 15:54:28 +0200

Op 20 sep. 2017 17:28 schreef "Pavel Lyalyakin" <
pavel.lyalyakin_at_visualsvn.com>:

Hello,

On Tue, Sep 19, 2017 at 12:42 AM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
>
> On Mon, Sep 18, 2017 at 6:00 PM, Pavel Lyalyakin
> <pavel.lyalyakin_at_visualsvn.com> wrote:
> > Hello,
> >
> > On Fri, Sep 15, 2017 at 11:57 PM, Johan Corveleyn <jcorvel_at_gmail.com>
wrote:
> >> On Thu, Sep 14, 2017 at 5:27 PM, Pavel Lyalyakin
> >> <pavel.lyalyakin_at_visualsvn.com> wrote:
> >> ...
> >>> I've spent some time to materialize the Quick Start document that I
> >>> think will be helpful for novice SVN users. At the moment, it provides
> >>> the most basic guidance which should be enough for "quick start".
> >>> However, it lacks "Viewing the history of changes" section that is not
> >>> ready yet. As of merging, I'd better provide a link to relevant
> >>> SVNBook sections. Merging is not a basic topic and should not be
> >>> described in a Quick Start guide, IMO.
> >>
> >> Hi Pavel,
> >>
> >> Nice! I've done a quick scan and it looks good in general. I'll try to
> >> go through it in detail this weekend, if I find some time.
> >>
> >> Your "quick start" is much larger than the old one (so we have to be
> >> careful that it's still as short as possible, to be "quick"), but I
> >> think it's good that you added some explanation of the basic concepts,
> >> and try to take the user along the most basic commands. The old "quick
> >> start" was more in the style of "here is some bait, don't be afraid to
> >> give it a try, and look for more docs". But now that I've read your
> >> patch (diagonally), I like it.
> >
> > Thank you. :)
> >
> > I consider the current patch as a basis for further work on this
> > document. I am not comfortable with rolling out a patch for
> > non-discussed document. But if we agree on the structure and topics
> > that should be covered, it is going to be easier to compose the doc
> > and review it.
>
> Ack. I didn't get around to a detailed review last weekend, and am
> totally swamped during this week, sorry. Maybe one of the other people
> on this list can go through it and provide some feedback?
>
> Otherwise, maybe I can pick it up again next weekend or the week after.

Got it. I'm thinking about making a new version of the patch taking
your suggestions into consideration till the end of the week. I guess
that I will send them in a separate new "[PATCH] ... thread" per patch
submission guidelines
(http://subversion.apache.org/docs/community-guide/general.html#patches).
That would be the correct way to send the patch to the mailing list
for a review.

Ack, that would be good.

-- 
Johan
Received on 2017-09-21 15:54:34 CEST

This is an archived mail posted to the Subversion Dev mailing list.