zsh-users
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@zsh.org>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Pre vcs versions of zsh
Date: Fri, 16 Apr 2021 21:35:15 +0200	[thread overview]
Message-ID: <50001-1618601715.767118@Z85c.YyLz.uKtN> (raw)
In-Reply-To: <CAH+w=7YSpmsh3m6XHhTgPApRAuhUi05Jxbi75KP3zsn0U5vjow@mail.gmail.com>

Bart Schaefer wrote:
> On Fri, Apr 16, 2021 at 7:33 AM Matthew Martin <[1]phy1729@gmail.com> wrote:
>
>     It is possible to add those versions to the history using git replace.

> I think I'd prefer PWS's suggestion of putting them on a vendor branch, rather
> than pasting them in front of Tanaka's initial revision, if the latter is what
> you accomplish by "replace".  (My limited-to-what-I've-previously-done-myself
> git experience is probably showing.)

Replacement references are just data blobs stored in git that tell it to
do things like pretend the parent commit of a commit is something
different. They have to be explicitly pushed and fetched. So essentially
they'd be an optional thing that would chain the separate vendor
branches together in the right order with the later commits.

The first tag in a linear history going back from the present seems to
be zsh-3.1.6-dev-21 but the repository does have tags going back to
3.1.5 with the various 3.1.5-pws-X releases apparently there. It'd be
really great if someone wants to work out what's going on there and tie
it in nicely with replacement references. Given that the -pws releases
were very frequent at the time, it might even be possible to dig patches
out of the -workers archives and reconstruct the history between them,
even if only partially with big fixup jumps. Older history can still be
very useful when trying to understand the code.

If anyone has other old data such as list archives it would be good to
collate it even if all we do is dump it on zero.zsh.org for now. As far
as possible we should try to put the old releases under old/ in the ftp
directory in their original form with original timestamps - using .shar
if that's what was in the usenet posts.

Oliver


  reply	other threads:[~2021-04-16 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15 22:56 Eric Cook
2021-04-15 23:37 ` Bart Schaefer
2021-04-16  0:31   ` Eric Cook
2021-04-16  1:11   ` Ray Andrews
2021-04-16  5:59 ` Stephane Chazelas
2021-04-16  6:18   ` Stephane Chazelas
2021-04-16 14:08   ` Daniel Shahaf
2021-04-16 14:23     ` Peter Stephenson
2021-04-16 14:33       ` Matthew Martin
2021-04-16 18:09         ` Bart Schaefer
2021-04-16 19:35           ` Oliver Kiddle [this message]
2021-04-16 15:03     ` Stephane Chazelas
2021-04-16 16:06       ` Stephane Chazelas
2021-04-16 16:51         ` Stephane Chazelas
2021-04-16 17:06         ` Daniel Shahaf

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=50001-1618601715.767118@Z85c.YyLz.uKtN \
    --to=opk@zsh.org \
    --cc=zsh-users@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).