From: Michael Haggerty <mhagger@alum.mit.edu>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Thomas Rast <trast@inf.ethz.ch>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Antoine Pelisse <apelisse@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH 4/4] fast-import: only store commit objects
Date: Tue, 07 May 2013 08:47:06 +0200 [thread overview]
Message-ID: <5188A36A.8000408@alum.mit.edu> (raw)
In-Reply-To: <CAMP44s3vGKv-Z6sx0sjAPH7_U1+AiJjFHjKz8ke+EUqW-u2Y=A@mail.gmail.com>
On 05/07/2013 06:47 AM, Felipe Contreras wrote:
> On Mon, May 6, 2013 at 10:27 PM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
>
>> You conjectured earlier that nobody uses blob marks, and I provided a
>> counterexample. Then you proposed a workaround that would require
>> changes to the cvs2git documentation, and I even explained how your
>> proposed workaround is not as flexible as the status quo.
>
> cvs2git does *not* need blob marks, it does not need marks at all.
>
> The use-case that you mentioned has nothing to do with cvs2git, in
> fact. I can be described as this:
>
> % ./generate-blobs > blobs
> % git fast-import --export-marks=marks < blobs
> % ./generate-commits > commits
> % git fast-import --import-marks=marks < commits
>
> In this example 'generate-commits' has no notion of marks at all, and
> 'git fast-import' doesn't need marks to process both blobs and
> commits.
The "generate-blobs" program generates a mark for each blob and
remembers the marks in a database. The "generate-commits" program reads
the marks from the database and incorporates them in the definitions of
the commits that it writes to its output. So yes, the program pair
*does* rely on marks for blobs being exported correctly.
I've tired of this discussion. I am quite sure that your change will
not be accepted, so I see no need to participate further. Please do not
interpret my silence as agreement with your quarrelsome arguments.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2013-05-07 6:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 4:31 [PATCH 0/4] fast-export: speed improvements Felipe Contreras
2013-05-03 4:31 ` [PATCH 1/4] fast-{import,export}: use get_sha1_hex() directly Felipe Contreras
2013-05-03 21:50 ` Junio C Hamano
2013-05-03 4:31 ` [PATCH 2/4] fast-export: improve speed by skipping blobs Felipe Contreras
2013-05-03 21:51 ` Junio C Hamano
2013-05-03 4:31 ` [PATCH 3/4] fast-export: don't parse all the commits Felipe Contreras
2013-05-03 21:54 ` Junio C Hamano
2013-05-04 0:06 ` Felipe Contreras
2013-05-04 19:22 ` Junio C Hamano
2013-05-03 4:31 ` [PATCH 4/4] fast-import: only store commit objects Felipe Contreras
2013-05-03 17:56 ` Thomas Rast
2013-05-03 18:23 ` Felipe Contreras
2013-05-06 10:28 ` Michael Haggerty
2013-05-06 10:32 ` Thomas Rast
2013-05-06 10:45 ` Michael Haggerty
2013-05-06 15:18 ` Junio C Hamano
2013-05-06 21:19 ` Felipe Contreras
2013-05-06 21:36 ` Felipe Contreras
2013-05-07 3:14 ` Michael Haggerty
2013-05-07 4:32 ` Johannes Schindelin
2013-05-07 4:36 ` Felipe Contreras
2013-05-07 2:58 ` Michael Haggerty
2013-05-07 4:37 ` Felipe Contreras
2013-05-06 21:04 ` Felipe Contreras
2013-05-07 3:27 ` Michael Haggerty
2013-05-07 4:39 ` Johannes Schindelin
2013-05-07 4:49 ` Felipe Contreras
2013-05-07 4:47 ` Felipe Contreras
2013-05-07 6:47 ` Michael Haggerty [this message]
2013-05-07 7:07 ` Felipe Contreras
2013-05-07 7:12 ` Junio C Hamano
2013-05-07 7:34 ` Michael Haggerty
2013-05-06 12:20 ` Johannes Schindelin
2013-05-06 21:06 ` Felipe Contreras
2013-05-03 22:08 ` Junio C Hamano
2013-05-03 22:19 ` Felipe Contreras
2013-05-03 23:45 ` Junio C Hamano
2013-05-04 0:01 ` Felipe Contreras
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=5188A36A.8000408@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=apelisse@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=trast@inf.ethz.ch \
/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).