From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Maintainer for git?
Date: Fri, 21 Feb 2014 17:52:00 -0000 [thread overview]
Message-ID: <87ha7sl95k.fsf@Rainer.invalid> (raw)
In-Reply-To: <20140221001833.GA10290@tastycake.net>
Adam Dinwoodie writes:
> I've tried this. I have `git cvsimport` seemingly working on the
> current Git 1.7.9 build, while my build reports the following SHA1
> error:
>
> ~~~~
> $ CVSROOT=:pserver:anoncvs@cygwin.com:/cvs/src git cvsimport -C cygwin -r cvs -k cygwin
> Initialized empty Git repository in /home/Adam/vcs/cygwin/.git/
> fatal: refs/remotes/cvs/master: not a valid SHA1
> fatal: master: not a valid SHA1
> fatal: You are on a branch yet to be born
> checkout failed: 32768
> ~~~~
I don't think that this error you see is related, but you absolutely
need cvsps version 2 for cvsimport to work correctly (or at all).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-02-21 16:31 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 3:43 David Conrad
2014-01-11 3:55 ` Steven Penny
2014-01-11 23:53 ` Adam Dinwoodie
2014-01-12 0:05 ` Steven Penny
2014-01-12 0:52 ` Adam Dinwoodie
2014-01-12 2:58 ` Steven Penny
2014-01-12 13:34 ` Adam Dinwoodie
2014-01-15 10:55 ` Adam Dinwoodie
2014-01-20 17:20 ` David Conrad
2014-01-20 23:26 ` Steven Penny
2014-01-21 1:26 ` Balaji Venkataraman
2014-01-21 1:31 ` Steven Penny
2014-01-22 18:25 ` David Conrad
2014-01-22 18:38 ` Adam Dinwoodie
2014-01-22 22:16 ` Balaji Venkataraman
2014-01-22 22:42 ` Chris O'Bryan
2014-01-23 10:51 ` Corinna Vinschen
2014-01-25 12:00 ` Corinna Vinschen
2014-01-25 21:18 ` David Rothenberger
2014-01-26 0:56 ` Balaji Venkataraman
2014-01-26 19:19 ` Adam Dinwoodie
2014-01-27 22:30 ` Balaji Venkataraman
2014-01-27 22:51 ` Balaji Venkataraman
2014-01-27 23:35 ` Andrey Repin
2014-01-28 0:11 ` Larry Hall (Cygwin)
2014-01-26 22:45 ` Steven Penny
2014-01-27 15:12 ` Chris O'Bryan
2014-01-27 21:14 ` David Conrad
2014-01-28 11:11 ` Corinna Vinschen
2014-01-29 15:35 ` Adam Dinwoodie
2014-01-29 17:14 ` David Conrad
2014-01-29 18:10 ` Corinna Vinschen
2014-02-04 21:10 ` David Conrad
2014-02-05 9:34 ` Corinna Vinschen
2014-01-29 18:10 ` Corinna Vinschen
2014-02-11 1:17 ` David Conrad
2014-02-11 18:50 ` Adam Dinwoodie
2014-02-11 19:45 ` David Boyce
2014-02-11 20:08 ` Larry Hall (Cygwin)
2014-02-11 20:39 ` Eric Blake
2014-01-23 16:27 ` Balaji Venkataraman
2014-01-23 16:31 ` Marco Atzeri
2014-01-23 17:29 ` Balaji Venkataraman
2014-01-23 17:50 ` Andrey Repin
2014-01-23 23:01 ` Balaji Venkataraman
2014-01-28 17:00 ` Charles Wilson
2014-01-28 17:09 ` Charles Wilson
2014-01-28 21:05 ` Andrey Repin
2014-01-29 13:58 ` Charles Wilson
2014-01-29 15:31 ` Christopher Faylor
2014-01-20 23:29 ` Steven Penny
2014-02-15 9:21 ` Alexander Kriegisch
2014-02-15 10:55 ` Adam Dinwoodie
2014-02-21 1:25 ` Adam Dinwoodie
2014-02-21 17:52 ` Achim Gratz [this message]
2014-02-26 9:57 ` Frank Fesevur
2014-04-14 19:40 ` David Conrad
2014-04-14 20:55 ` Adam Dinwoodie
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=87ha7sl95k.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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).