From: Sverre Rabbelier <srabbelier@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Git List <git@vger.kernel.org>
Subject: option directive to fast-import
Date: Sat, 1 Aug 2009 18:29:10 -0700 [thread overview]
Message-ID: <fabb9a1e0908011829j3843c132ka5081d994aad973f@mail.gmail.com> (raw)
Heya,
What would you think of a 'option' directive to fast-import?
'option' SP <option> SP <value> LF
Where <option> is:
import-marks
export-marks
force_update
quiet
stats
date-format
depth
active-branches
export-pack-edges
I just checked them all, and as far as I can see, as long as the
option directives come before any data, there should be no negative
side-effects to setting these values 'late'. The upside would be that
the frontend can tell git fast-import it's preferences, so that the
user does not have to type a humongous commandline, but instead can
suffice to just go with 'foo fast-export | git fast-import'. Of
course, the user might want to override these options manually, so the
option directives should only be honored if no commandline flag is
given.
Would you accept such a patch? If yes, I'll whip something up :).
--
Cheers,
Sverre Rabbelier
next reply other threads:[~2009-08-02 1:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 1:29 Sverre Rabbelier [this message]
2009-08-02 5:06 ` [RFC PATCH 0/3] fast-import: add option command Sverre Rabbelier
2009-08-02 5:06 ` [RFC PATCH 1/2] fast-import: put option parsing code in seperate functions Sverre Rabbelier
2009-08-02 5:06 ` [RFC PATCH 2/2] fast-import: add option command Sverre Rabbelier
2009-08-02 5:06 ` [RFC PATCH 3/3] fast-import: test the new " Sverre Rabbelier
2009-08-02 7:09 ` [RFC PATCH v1a 1/3] fast-import: put option parsing code in seperate functions Sverre Rabbelier
2009-08-03 0:15 ` [RFC PATCH 0/3] fast-import: add option command Shawn O. Pearce
2009-08-03 4:31 ` Sverre Rabbelier
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=fabb9a1e0908011829j3843c132ka5081d994aad973f@mail.gmail.com \
--to=srabbelier@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 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).