From: Junio C Hamano <gitster@pobox.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: can we allow -t abbreviation for --track in 'git branch'
Date: Sat, 09 May 2009 08:15:52 -0700 [thread overview]
Message-ID: <7vab5m9ujb.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <slrnh0agtv.4rv.sitaramc@sitaramc.homelinux.net> (Sitaram Chamarty's message of "Sat\, 9 May 2009 08\:50\:07 +0000 \(UTC\)")
Sitaram Chamarty <sitaramc@gmail.com> writes:
> Would it make sense to teach "git branch" the short option
> "-t" the same way that "git checkout" knows it, (ie., as an
> abbreviation for "--track")?
>
> I use both frequently, and often forget that in "git branch"
> the short option does not work.
>
> If people think it's OK I'll submit a patch (code and doc).
I have <20090428152119.GA18935@atc.tcs.com> (aka $gmane/117790) in my
inbox.
next prev parent reply other threads:[~2009-05-09 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 8:50 can we allow -t abbreviation for --track in 'git branch' Sitaram Chamarty
2009-05-09 9:17 ` Nicolas Sebrecht
2009-05-09 15:15 ` Junio C Hamano [this message]
2009-05-10 4:23 ` Sitaram Chamarty
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=7vab5m9ujb.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sitaramc@gmail.com \
/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