From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Felipe Contreras <felipe.contreras@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] fast-import: add ignore non-existent files option.
Date: Tue, 02 Sep 2008 00:36:21 -0700 [thread overview]
Message-ID: <7v8wubm22y.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080902053503.GD13248@spearce.org> (Shawn O. Pearce's message of "Mon, 1 Sep 2008 22:35:03 -0700")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> Junio C Hamano <gitster@pobox.com> wrote:
> ...
>> I think selective loosening of consistency check makes sense very much,
>> but I have been wondering if these should be command line options.
>>
>> The only example we saw so far is about output from one exporter. Perhaps
>> it should be given to fast-import as initial set of commands ("#pragma"!)
>> that describes the nature of the input file?
>
> Yea, I briefly considered that when I added the timestamp format
> option. I didn't bother because it was a single option and I figured
> most frontends start git-fast-import directly. But with this being
> added a "format pragrma header thingy" makes a lot of sense.
Oh, I did not mean to suggest hiding it as a comment to silently allow
older fast-import slurp such input and produce broken results.
For input that needs such loosened error checking, old fast-import won't
produce correct results _anyway_, so I would agree that making these
things into explicit commands to cause older fast-import to error out
would make a lot more sense.
next prev parent reply other threads:[~2008-09-02 7:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 13:20 [PATCH 1/1] fast-import: show a warning for non-existent files Felipe Contreras
2008-09-01 19:04 ` Junio C Hamano
2008-09-01 21:58 ` Felipe Contreras
2008-09-01 19:25 ` Shawn O. Pearce
2008-09-01 22:01 ` Felipe Contreras
2008-09-01 22:30 ` [PATCH] fast-import: add ignore non-existent files option Felipe Contreras
2008-09-01 22:38 ` Shawn O. Pearce
2008-09-01 22:52 ` Felipe Contreras
2008-09-02 4:39 ` Shawn O. Pearce
2008-09-02 4:53 ` Junio C Hamano
2008-09-02 5:35 ` Shawn O. Pearce
2008-09-02 7:36 ` Junio C Hamano [this message]
2008-09-02 7:48 ` Felipe Contreras
2008-09-01 23:04 ` Junio C Hamano
2008-09-01 23:25 ` Felipe Contreras
2008-09-02 2:07 ` Junio C Hamano
2008-09-02 7:57 ` 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=7v8wubm22y.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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.
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.