From: Frank Terbeck <ft@bewatermyfriend.org>
To: Wayne Davison <wayned@users.sourceforge.net>
Cc: zsh-workers@sunsite.dk
Subject: Re: Git mirror at SF
Date: Sun, 26 Apr 2009 12:29:37 +0200 [thread overview]
Message-ID: <20090426102937.GA4326@fsst.voodoo.lan> (raw)
In-Reply-To: <20090404221212.GA21390@blorf.net>
Wayne Davison <wayned@users.sourceforge.net>:
[...]
> Today I implemented a better fix for the cvsps code, and am testing that
> to see how it will handle the new commits that show up. While that is
> going on you may see a delay in new cvs commits showing up in the git
> repo.
>
> When I'm done, I'm going to push a brand new git repository because my
> new cvsps code managed to join together a split commit into a proper
> changeset, and I want to update the repository with that change.
>
> For anyone who grabs changes via "git pull --rebase", git should sync up
> just fine when the new repository goes out (I tested it, and it uses a
> 3-way merge for the spot where the 2 commits become one, and the end
> result is identical to a fresh pull).
Hi Wayne,
Currently, the git repository's history seems a little off (although
the repo's contents appear to be correct).
a) I don't see any new tags (like one for 4.3.10-dev-3).
b) I think the history of the git repository should be linear,
shouldn't it? But year it seems to be broken up in one or two
places, see: http://ft.bewatermyfriend.org/tmp/zshgithist.png
Note that commits (alongside their tags) from November 2008 precede
commits from January 2008 in that history.
I am sure, this was not the case in earlier git imports, since I
sometimes used the git history to check when a certain change was
made in zsh.
This is a newly cloned repository, to avoid possible problems when
using --rebase when pulling.
My current git version is: 1.6.2.2.446.gfbdc0
Any ideas? Or am I misjudging something here?
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2009-04-26 10:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 19:23 Git mirror at SF + link to "repos" script Wayne Davison
2009-03-14 21:51 ` Frank Terbeck
2009-03-14 23:22 ` Wayne Davison
2009-03-15 5:59 ` Clint Adams
2009-03-15 16:54 ` Wayne Davison
2009-03-15 19:56 ` Clint Adams
2009-03-15 21:20 ` Wayne Davison
2009-04-04 22:12 ` Git mirror at SF Wayne Davison
2009-04-05 20:41 ` Wayne Davison
2009-04-26 10:29 ` Frank Terbeck [this message]
2009-04-26 16:05 ` Wayne Davison
2009-04-26 17:44 ` Frank Terbeck
2009-04-27 16:19 ` Wayne Davison
2009-03-14 22:14 ` Git mirror at SF + link to "repos" script Ingmar Vanhassel
2009-03-15 1:33 ` Wayne Davison
[not found] ` <20091204045055.GA13426@scru.org>
2009-12-04 17:16 ` Wayne Davison
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=20090426102937.GA4326@fsst.voodoo.lan \
--to=ft@bewatermyfriend.org \
--cc=wayned@users.sourceforge.net \
--cc=zsh-workers@sunsite.dk \
/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).