All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Taht <mike.taht@timesys.com>
To: git@vger.kernel.org
Subject: git options
Date: Mon, 18 Apr 2005 02:23:03 -0700	[thread overview]
Message-ID: <42637C77.5070101@timesys.com> (raw)
In-Reply-To: <20050417213632.1f099ff9.pj@sgi.com>

Would it be useful at this point to make common and centralize some/most 
of the various options that control git? (as well as add some useful 
ones). Something like:

struct _git_opt {
         int verbose:1;
         int debug:1;
	int dry-run:1;
         int should_block:1;
         int remove_lock:1;
         int allow_add:1;
         int allow_remove:1;
         int null_termination:1;
         int show_cached:1;
         int show_deleted:1;
         int show_others:1;
         int show_ignored:1;
         int show_stage:1;
         int show_unmerged:1;
         int show_edges:1;
         int show_unreachable:1;
         int basemask:1;
         int recursive:1;
         int force_filename:1;
         int force:1;
         int quiet:1;
         int stage:1;
};


-- 

Mike Taht


   "Avoid letting temper block progress; keep cool.
	-- William Feather"

      reply	other threads:[~2005-04-18  9:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-16 13:22 using git directory cache code in darcs? David Roundy
2005-04-16 13:31 ` Ingo Molnar
2005-04-16 14:28 ` Junio C Hamano
2005-04-16 22:43 ` Linus Torvalds
2005-04-17 12:17   ` David Roundy
2005-04-17 16:24     ` Linus Torvalds
2005-04-17 16:49       ` Mike Taht
2005-04-17 22:37       ` Nomad Arton
2005-04-17 23:23         ` Junio C Hamano
2005-04-18  2:00           ` Paul Jackson
2005-04-18  2:56       ` Paul Jackson
2005-04-18  3:06         ` Linus Torvalds
2005-04-18  4:36           ` Paul Jackson
2005-04-18  9:23             ` Mike Taht [this message]

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=42637C77.5070101@timesys.com \
    --to=mike.taht@timesys.com \
    --cc=git@vger.kernel.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.