From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Cc: Johan Herland <johan@herland.net>,
barkalow@iabervon.org, gitster@pobox.com
Subject: [RFCv2 10/12] Introduce a 'marks <filename>' feature to the foreign transport code
Date: Fri, 31 Jul 2009 12:00:30 +0200 [thread overview]
Message-ID: <1249034432-31437-11-git-send-email-johan@herland.net> (raw)
In-Reply-To: <1249034432-31437-1-git-send-email-johan@herland.net>
The 'marks' feature is reported by the vcs helper when it requires the
fast-import marks database to loaded/saved by the git-fast-import process
that is executed by the foreign transport machinery. The feature is
advertised along with exactly one argument: the location of the file
containing the marks database.
Signed-off-by: Johan Herland <johan@herland.net>
---
Documentation/git-vcs.txt | 8 ++++++++
transport-foreign.c | 32 ++++++++++++++++++++++++++++++--
2 files changed, 38 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-vcs.txt b/Documentation/git-vcs.txt
index 85656d4..75815ba 100644
--- a/Documentation/git-vcs.txt
+++ b/Documentation/git-vcs.txt
@@ -65,6 +65,14 @@ there may be other restrictions on what may be exported.
FEATURES
--------
+'marks' filename::
+ Helper requires the marks from a git-fast-import run to be loaded
+ from, and saved to, the given filename. When this "feature" is
+ advertised, each git-fast-import run must load and save the
+ internal marks database (see the --import-marks and --export-marks
+ option to git-fast-import for more details) located at the given
+ filename.
+
'export'::
Helper supports exporting commits, at least exporting
non-merge commits whose parents are not the parents of any
diff --git a/transport-foreign.c b/transport-foreign.c
index be0a587..ae9cb9a 100644
--- a/transport-foreign.c
+++ b/transport-foreign.c
@@ -11,6 +11,7 @@ struct foreign_data
struct child_process importer;
/* capabilities */
+ char *marks_filename;
unsigned export:1;
unsigned export_branch:1;
unsigned export_merges:1;
@@ -38,7 +39,12 @@ static void get_foreign_capabilities(struct foreign_data *fdata)
*eon = '\0';
/* parse features */
- if (!strcmp(buf.buf, "export"))
+ if (!strcmp(buf.buf, "marks")) {
+ if (!eon)
+ die("Feature 'marks' requires an argument");
+ fdata->marks_filename = xstrdup(eon + 1);
+ }
+ else if (!strcmp(buf.buf, "export"))
fdata->export = 1;
else if (!strcmp(buf.buf, "export-branch"))
fdata->export_branch = 1;
@@ -82,6 +88,7 @@ static int disconnect_foreign(struct transport *transport)
write(fdata->importer.in, "\n", 1);
close(fdata->importer.in);
finish_command(&fdata->importer);
+ free(fdata->marks_filename);
free(fdata);
transport->data = NULL;
}
@@ -91,10 +98,13 @@ static int disconnect_foreign(struct transport *transport)
static int fetch_refs_via_foreign(struct transport *transport,
int nr_heads, struct ref **to_fetch)
{
+ struct foreign_data *fdata;
struct child_process *importer;
struct child_process fastimport;
struct ref *posn;
+ struct strbuf export_marks, import_marks;
int i, count;
+ FILE *f;
count = 0;
for (i = 0; i < nr_heads; i++) {
@@ -105,12 +115,28 @@ static int fetch_refs_via_foreign(struct transport *transport,
}
if (count) {
importer = get_importer(transport);
+ fdata = (struct foreign_data *) transport->data;
+ strbuf_init(&export_marks, 0);
+ strbuf_init(&import_marks, 0);
memset(&fastimport, 0, sizeof(fastimport));
fastimport.in = importer->out;
- fastimport.argv = xcalloc(3, sizeof(*fastimport.argv));
+ fastimport.argv = xcalloc(5, sizeof(*fastimport.argv));
fastimport.argv[0] = "fast-import";
fastimport.argv[1] = "--quiet";
+ if (fdata->marks_filename) {
+ strbuf_addf(&export_marks, "--export-marks=%s",
+ fdata->marks_filename);
+ fastimport.argv[2] = export_marks.buf;
+
+ f = fopen(fdata->marks_filename, "r");
+ if (f) {
+ strbuf_addf(&import_marks, "--import-marks=%s",
+ fdata->marks_filename);
+ fastimport.argv[3] = import_marks.buf;
+ fclose(f);
+ }
+ }
fastimport.git_cmd = 1;
start_command(&fastimport);
@@ -124,6 +150,8 @@ static int fetch_refs_via_foreign(struct transport *transport,
}
disconnect_foreign(transport);
finish_command(&fastimport);
+ strbuf_release(&export_marks);
+ strbuf_release(&import_marks);
}
for (i = 0; i < nr_heads; i++) {
posn = to_fetch[i];
--
1.6.4.rc3.138.ga6b98.dirty
next prev parent reply other threads:[~2009-07-31 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 10:00 [RFCv2 00/12] Foreign VCS helper program for CVS repositories Johan Herland
2009-07-31 10:00 ` [RFCv2 01/12] Allow late reporting of fetched hashes Johan Herland
2009-07-31 10:00 ` [RFCv2 02/12] Document details of transport function APIs Johan Herland
2009-07-31 10:00 ` [RFCv2 03/12] Add option for using a foreign VCS Johan Herland
2009-07-31 10:00 ` [RFCv2 04/12] Add specification of git-vcs-* helper programs Johan Herland
2009-07-31 10:00 ` [RFCv2 05/12] Use a function to determine whether a remote is valid Johan Herland
2009-07-31 10:00 ` [RFCv2 06/12] Allow programs to not depend on remotes having urls Johan Herland
2009-07-31 10:00 ` [RFCv2 07/12] Add a transport implementation using git-vcs-* helpers Johan Herland
2009-07-31 10:00 ` [RFCv2 08/12] Preliminary clarifications to git-vcs documentation Johan Herland
2009-07-31 10:00 ` [RFCv2 09/12] Teach foreign transport code to perform the "capabilities" command Johan Herland
2009-07-31 10:00 ` Johan Herland [this message]
2009-07-31 10:00 ` [RFCv2 12/12] Add simple test cases of git-vcs-cvs functionality Johan Herland
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=1249034432-31437-11-git-send-email-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 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 NNTP newsgroup(s).