Re: Access to CVS

[Peter Stephenson <p.stephenson@xxxxxxxxxxx>]

On Fri, 14 Dec 2012 15:44:22 +0100
Oliver Kiddle <okiddle@xxxxxxxxxxx> wrote:
> Peter Stephenson wrote:
> > It might be useful to give a sample list of explicit git commands
> > to use at each stage, in particular what you'd do for an initial
> > commit, for updating the commit with the mailing list ID, for any
> > kind of trickery to reduce the number of commits that get pushed,
> > and for pushing it back (as this is for those new to git you can
> > assume the relationship between the local archive and the remote
> > master is simple and let the git gurus do the clever stuff).
> 
> Is that a suggestion for the contents of Etc/zsh-development-guide or
> just a case that it'd be useful. I'm assuming the latter - it's not
> like we have an introduction to CVS, autoconf, C etc in the file.
> Anyway, in that case it seems Phil and Frank have already answered
> this.

If there was a compact enough summary to go in the development guide,
that would be great, though it's not crucial.  The problem is git allows
a zillion different ways of doing it whereas in CVS you were restricted
to committing what you've changed, and that was it.

I'm still hoping for a simple, straightforward list of the basic
commands you'd need to use *not* involving the manifold ramifications of
branches here, there and everywhere.  Presumably this isn't more than
half a dozen commands or so.

pws