unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Git import issues
Date: Mon, 07 Apr 2008 01:00:57 +0200	[thread overview]
Message-ID: <87skxyziza.fsf@gnu.org> (raw)

Hi,

I discovered scary things in our new Git repository, more precisely in
the `branch_release-1-8' branch, and I'm wondering how I can have missed
them earlier given that I already committed and rebuilt things in that
branch earlier.

Basically "master" is OK, but commits are missing in branches,
apparently only commits that add or remove files.

For example, `branch_release-1-8' lacks "{check,benchmark}-guile.in" and
"doc/r5rs/r5rs.texi"; conversely, it has "acconfig.h", an old file that
had been deleted long ago.

Han-Wen's import does not have these problems [0], and the CVS repo
either [1].  Eric Blake reported similar problems about his import of
GNU M4 a while back [2].

I emailed Han-Wen and Eric to get advice from them.  I'm also
considering other methods such as using `cvs2git' [3] to do the import
(which Dale P. Smith actually suggested on IRC some time ago, although I
didn't see any compelling reason to use it back then...).

I apologize for this problem and the inconvenience it causes, which
demonstrate my excess of confidence on that matter.  I'll try hard to
fix it ASAP.  Hopefully it should be fairly easy to recommit the few
patches that were committed to the Git repo if we need to start with a
fresh import.

Thanks,
Ludovic.

[0] http://repo.or.cz/w/guile.git?a=tree;h=0e438375ff6f64cbd569e896a976ae1ddb099650;hb=0e438375ff6f64cbd569e896a976ae1ddb099650
[1] http://cvs.savannah.gnu.org/viewvc/guile/guile/guile-core/?hideattic=0
[2] http://thread.gmane.org/gmane.comp.version-control.git/58817
[3] http://cvs2svn.tigris.org/cvs2git.html





             reply	other threads:[~2008-04-06 23:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06 23:00 Ludovic Courtès [this message]
2008-04-07 19:57 ` Git import issues Ludovic Courtès
2008-04-07 22:27   ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=87skxyziza.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).