All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Herland <johan@herland.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [RFC 00/11] Foreign VCS helper program for CVS repositories
Date: Mon, 27 Jul 2009 20:11:19 +0200	[thread overview]
Message-ID: <200907272011.19430.johan@herland.net> (raw)
In-Reply-To: <alpine.LNX.2.00.0907271251280.2147@iabervon.org>

On Monday 27 July 2009, Daniel Barkalow wrote:
> On Mon, 27 Jul 2009, Johan Herland wrote:
> > This series is a first draft towards implementing a foreign VCS
> > helper program for CVS.
> >
> > It is based on the 'db/foreign-scm' and 'jh/notes' topics in 'pu'.
> > As such, this patch series should apply cleanly to current 'pu'.
> >
> > The first 4 patches supply the necessary parts of Daniel Barkalow's
> > foreign-scm topic that has not yet been merged to 'pu' (i.e.
> > everything remaining in Daniel's original patch series, except the
> > p4-specific stuff).
>
> I've got some changes to this series in the works; I just made a few
> changes to share the transport-side code for interacting with the
> helper with the transport-side code for interacting with
> native-object helpers. Mainly, this means starting each line in the
> "list" response with "?" to indicate that you don't know the hash,
> since the protocol is trying to be compatible with cases where you do
> know.

No problem. I'm actually considering whether I should rewrite the CVS 
helper to a full-fledged git-shim (btw, thanks for the shim work; it 
looks really promising). I would still probably have to use 
git-fast-import, but I would have more control over the fast-import 
process (e.g. by closing the fast-import process myself, I could 
simplify the code maintaining the marks database).

With the git-shim feature already having found an excellent use case 
(the HTTP fetcher), how do you see the future for the foreign-scm 
topic? I like the idea of rewriting foreign-scm on top of git-shim, but 
is there anything substantial _left_ in foreign-scm after such a 
rewrite?

> > Next, there are 3 patches tweaking and expanding the git-vcs API
> > (with corresponding implementations in the foreign transport code)
> > to adjust for the CVS helper's needs.
>
> These make sense to me. I assume you're planning to support exporting
> in some ways, but haven't got it working yet?

Indeed. The current version is only a first draft that fetches 
successfully from simple toy repositories (but probably not many 
real-world CVS repos). I hope to support both fetching and pushing to 
real-world CVS repos at some point.


Have fun! :)

...Johan

-- 
Johan Herland, <johan@herland.net>
www.herland.net

  reply	other threads:[~2009-07-27 18:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27  1:04 [RFC 00/11] Foreign VCS helper program for CVS repositories Johan Herland
2009-07-27  1:04 ` [RFC 01/11] Add specification of git-vcs-* helper programs Johan Herland
2009-07-27  1:04 ` [RFC 02/11] Use a function to determine whether a remote is valid Johan Herland
2009-07-27  1:04 ` [RFC 03/11] Allow programs to not depend on remotes having urls Johan Herland
2009-07-27 18:55   ` Junio C Hamano
2009-07-27 19:33     ` Daniel Barkalow
2009-07-29  8:57   ` Alex Riesen
2009-07-30  0:24     ` Johan Herland
2009-07-27  1:04 ` [RFC 04/11] Add a transport implementation using git-vcs-* helpers Johan Herland
2009-07-27  1:04 ` [RFC 05/11] Refactor path name parsing into new function: get_path_str() Johan Herland
2009-07-27  1:04 ` [RFC 06/11] Add support for mark references as path names Johan Herland
2009-07-27 14:12   ` Shawn O. Pearce
2009-07-27 18:26     ` Johan Herland
2009-07-27 18:35       ` Shawn O. Pearce
2009-07-28  1:43         ` [RFC 06/11 v2] fast-import: Add support for importing commit notes Johan Herland
2009-07-29  2:18           ` Junio C Hamano
2009-07-29  2:41             ` Johan Herland
2009-07-29 14:26               ` Shawn O. Pearce
2009-07-29 16:20                 ` Junio C Hamano
2009-07-30  0:29                   ` Johan Herland
2009-07-30  2:35                     ` Junio C Hamano
2009-07-29 18:56           ` Junio C Hamano
2009-07-29 23:08             ` Johan Herland
2009-07-27  1:04 ` [RFC 07/11] Preliminary clarifications to git-vcs documentation Johan Herland
2009-07-27  1:04 ` [RFC 08/11] Teach foreign transport code to perform the "capabilities" command Johan Herland
2009-07-27  1:04 ` [RFC 09/11] Introduce a 'marks <filename>' feature to the foreign transport code Johan Herland
2009-07-27  1:04 ` [RFC 11/11] Add simple test cases of git-vcs-cvs functionality Johan Herland
2009-07-27 17:27 ` [RFC 00/11] Foreign VCS helper program for CVS repositories Daniel Barkalow
2009-07-27 18:11   ` Johan Herland [this message]
2009-07-27 18:58     ` Daniel Barkalow

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=200907272011.19430.johan@herland.net \
    --to=johan@herland.net \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 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.