zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: document git in Etc/zsh-development-guide
Date: Thu, 20 Dec 2012 07:55:09 -0800	[thread overview]
Message-ID: <121220075509.ZM30659@torch.brasslantern.com> (raw)
In-Reply-To: <22690.1356010707@thecus.kiddle.eu>

On Dec 20,  2:38pm, Oliver Kiddle wrote:
}
} Phil Pennock wrote:
} > We also now have *two* git workflow sections, contradicting each other.
} 
} We already had two contractory workflows and that, more so than the
} sections, is what needs resolving. Unfortunately it is harder to
} consolidate two contradictory workflows than to take one as a baseline
} and discuss how it can be improved or where the interpretation of the
} consensus from earlier discussion was wrong.

See, this is exactly what I was hoping would NOT happen when I suggested
that someone [*] summarize to the mailing list and everyone agree on the
summary before we started committing changes to the development guide.
I suppose one of the arguments for changing to git is that it makes this
kind of thing easier to sort out, because commits can be shared/reviewed
before being pushed to the master repository.

Thank goodness PWS tagged CVS when the -test1 tarball was created.  I'm
half tempted to cvs-admin-o back to that revision so we can start over.

[*] By which I imply someone who understands git thoroughly enough to
comprehend/consolidate everything that was being suggested, for which
I am not qualified.

Incidentally, the IP address of zsh.cvs.sourceforge.net appears to have
changed recently.  Maybe whatever it was Phil meant about SourceForge
having broken CVS, has been corrected now?  (Not that this changes any
plans.)


  parent reply	other threads:[~2012-12-20 15:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17  8:52 Phil Pennock
2012-12-17  9:59 ` Frank Terbeck
2012-12-17 11:22   ` Phil Pennock
2012-12-17 10:15 ` Peter Stephenson
2012-12-17 11:00   ` Phil Pennock
2012-12-17 13:50     ` Oliver Kiddle
2012-12-18  9:36       ` Phil Pennock
2012-12-18 16:46         ` Peter Stephenson
2012-12-19 14:06         ` Oliver Kiddle
2012-12-20  9:57           ` Phil Pennock
2012-12-20 13:38             ` Oliver Kiddle
2012-12-20 13:55               ` Peter Stephenson
2012-12-20 15:55               ` Bart Schaefer [this message]
2012-12-20 18:42                 ` Peter Stephenson
2012-12-20 20:58               ` Phil Pennock
2012-12-17 14:17   ` Benjamin R. Haskell
2012-12-18  9:33     ` Phil Pennock
2012-12-18 14:11       ` Benjamin R. Haskell
2012-12-18 20:37         ` zsh.org & patch archive Phil Pennock
2012-12-19  6:49           ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=121220075509.ZM30659@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).