threads / patch / 20500

patch, 8 partsForeign VCS helpers

Subject: [PATCH 0/8] Foreign VCS helpers

## tl;dr

2 messages between Aug 9, 2009 and Aug 9, 2009. Diffs are folded; open one to read it.

replies: 1people: 2as markdown or json

Daniel Barkalow· Aug 9, 2009, 19:28 UTC · lore

This is a replacement for the db/foreign-scm series in pu, now based on next. The behavior specified for helpers is the same, so I'm not reposting the particular helpers this time.

Daniel Barkalow (7):
  Use a clearer style to issue commands to remote helpers
  Use a function to determine whether a remote is valid
  Allow fetch to modify refs
  Allow programs to not depend on remotes having urls
  Add a config option for remotes to specify a foreign vcs
  Add support for "import" helper command
  Allow helpers to report in "list" command that the ref is unchanged
Johan Herland (1):
  Allow helpers to request marks for fast-import
 Documentation/config.txt             |    4 +
 Documentation/git-remote-helpers.txt |   22 ++++++-
 builtin-clone.c                      |    6 +-
 builtin-fetch.c                      |   19 +++--
 builtin-ls-remote.c                  |    4 +-
 builtin-push.c                       |   54 +++++++++-----
 remote.c                             |   15 +++-
 remote.h                             |    2 +
 transport-helper.c                   |  129 ++++++++++++++++++++++++++++++----
 transport.c                          |   21 ++++--
 transport.h                          |   41 ++++++++++-
 11 files changed, 261 insertions(+), 56 deletions(-)
Johan Herland· Aug 9, 2009, 21:31 UTC · re: Daniel Barkalow · lore

Re: [PATCH 0/8] Foreign VCS helpers

On Sunday 09 August 2009, Daniel Barkalow wrote:
> This is a replacement for the db/foreign-scm series in pu, now based
> on next. The behavior specified for helpers is the same, so I'm not
> reposting the particular helpers this time.
Thanks. I'll clean up and rebase my CVS series on top of this.
Thanks again for your work. Really appreciated!
Have fun! :)
...Johan
-- 
Johan Herland, <johan@herland.net>
www.herland.net

← back to recent threads