From: Jim Meyering <jim@meyering.net>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Info about available CVS/Arch/Git branches
Date: Mon, 13 Aug 2007 13:50:55 +0200 [thread overview]
Message-ID: <878x8firfk.fsf@meyering.net> (raw)
In-Reply-To: <86hcn3ka5f.fsf@lola.quinscape.zz> (David Kastrup's message of "Mon\, 13 Aug 2007 12\:21\:16 +0200")
David Kastrup <dak@gnu.org> wrote:
> Jim Meyering <jim@meyering.net> writes:
>
>> David Kastrup <dak@gnu.org> wrote:
>>
>> You might want to look at how that is handled in the git <-> p4
>> mirroring code in git's contrib/fast-import/*.
>>
>> BTW, in the last week, I changed things so that branches in the git
>> repository
>
> Which repository are you talking about right now?
AFAIK, there is only one public git mirror of the emacs CVS repository:
http://git.sv.gnu.org/gitweb/?p=emacs.git
git-clone git://git.sv.gnu.org/emacs.git
>> are now pushed into the public emacs.git. Before, I'd been pushing
>> only the trunk ("master").q
>
> I presume that emacs.git is just a mirror, and nothing gets committed
> back into CVS either via Miles' arch or directly?
Yep. That's what "mirror" means to me, too.
However, if you make changes on a private git branch,
it's easy (git-cvsexportcommit) to mirror them back into a cvs commit.
next prev parent reply other threads:[~2007-08-13 11:50 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 [this message]
2007-08-13 13:05 ` Andreas Schwab
2007-08-13 13:07 ` Jim Meyering
2007-08-13 13:28 ` Randal L. Schwartz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878x8firfk.fsf@meyering.net \
--to=jim@meyering.net \
--cc=dak@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.