From: merlyn@stonehenge.com (Randal L. Schwartz)
To: emacs-devel@gnu.org
Subject: Re: Info about available CVS/Arch/Git branches
Date: Mon, 13 Aug 2007 06:28:01 -0700 [thread overview]
Message-ID: <86bqdbk1i6.fsf@blue.stonehenge.com> (raw)
In-Reply-To: 87absvh9bw.fsf@meyering.net
>>>>> "Jim" == Jim Meyering <jim@meyering.net> writes:
>> There is a problem with this repo: for some time all commits have been
>> made to a subdirectory emacs.
Jim> Thanks, I know.
Jim> I'm working on it now.
Weird. That was also the breakage on the version I was tracking at repo.or.cz
(which I ensured was turned off because it was broken and the "maintainer" is
AWOL). Were they both from the same source, or both broken in the same way
because of problems with cvs2git?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2007-08-13 13:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 15:59 Info about available CVS/Arch/Git branches Stefan Monnier
2007-08-09 20:57 ` Reiner Steib
2007-08-12 3:45 ` Michael Olson
2007-08-12 9:10 ` Andreas Schwab
2007-08-13 9:42 ` David Kastrup
2007-08-13 10:06 ` Jim Meyering
2007-08-13 10:21 ` David Kastrup
2007-08-13 10:52 ` dhruva
2007-08-13 11:05 ` David Kastrup
2007-08-18 9:20 ` Andreas Schwab
2007-08-18 10:39 ` dhruva
2007-08-20 4:22 ` Miles Bader
2007-08-20 6:12 ` dhruva
2007-08-13 11:50 ` Jim Meyering
2007-08-13 13:05 ` Andreas Schwab
2007-08-13 13:07 ` Jim Meyering
2007-08-13 13:28 ` Randal L. Schwartz [this message]
2007-08-13 14:46 ` Jim Meyering
2007-08-13 16:41 ` Jim Meyering
2007-08-13 14:32 ` Andreas Schwab
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86bqdbk1i6.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=emacs-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).