git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julian Phillips <julian@quantumfyre.co.uk>
To: git@vger.kernel.org
Subject: [PATCH 0/2] git-branch: improve command line handling of --abbrev=
Date: Sat,  3 Mar 2007 00:31:15 +0000	[thread overview]
Message-ID: <11728818772136-git-send-email-julian@quantumfyre.co.uk> (raw)

When playing with git-branch I discovered that it handled the --abbrev= option
differently to other commands, which surprised me.

This update the parsing code in builtin_branch.c to be the same as
setup_revisions in revision.c, and documents the new --no-abbrev option.

-- 
Julian

             reply	other threads:[~2007-03-03  0:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-03  0:31 Julian Phillips [this message]
     [not found] ` <028df363480685d1fe1ab84a99b2573dda853440.1172881822.git.julian@quantumfyre.co.uk>
2007-03-03  0:31   ` [PATCH 1/2] git-branch: improve abbreviation of sha1s in verbose mode Julian Phillips
     [not found]   ` <4a1baac35d2826499a1fa4c1439b7740be23e7b5.1172881822.git.julian@quantumfyre.co.uk>
2007-03-03  0:31     ` [PATCH 2/2] git-branch: document new --no-abbrev option Julian Phillips

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=11728818772136-git-send-email-julian@quantumfyre.co.uk \
    --to=julian@quantumfyre.co.uk \
    --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 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).