All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2013, #03; Wed, 11)
Date: Thu, 12 Sep 2013 08:24:21 -0700	[thread overview]
Message-ID: <xmqqa9jiqd0a.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <52315D02.9060206@viscovery.net> (Johannes Sixt's message of "Thu, 12 Sep 2013 08:19:46 +0200")

Johannes Sixt <j.sixt@viscovery.net> writes:

> Am 9/12/2013 1:32, schrieb Junio C Hamano:
>> * jc/ref-excludes (2013-09-03) 2 commits
>>  - document --exclude option
>>  - revision: introduce --exclude=<glob> to tame wildcards
>> 
>>  People often wished a way to tell "git log --branches" (and "git
>>  log --remotes --not --branches") to exclude some local branches
>>  from the expansion of "--branches" (similarly for "--tags", "--all"
>>  and "--glob=<pattern>").  Now they have one.
>> 
>>  Will merge to 'next'.
>
> Please don't. This is by far not ready. It needs a different approach to
> support --exclude= in rev-parse.

Thanks for a dose of sanity. I didn't look at rev-parse. I vaguely
recall somebody offered follow-ups (was it you?) and at that point
I placed this on the back-burner.

  reply	other threads:[~2013-09-12 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 23:32 What's cooking in git.git (Sep 2013, #03; Wed, 11) Junio C Hamano
2013-09-12  5:36 ` Jeff King
2013-09-12 18:14   ` Junio C Hamano
2013-09-12  6:19 ` Johannes Sixt
2013-09-12 15:24   ` Junio C Hamano [this message]
2013-09-13  5:30     ` Johannes Sixt
2013-09-13  5:56       ` Junio C Hamano

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=xmqqa9jiqd0a.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    /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.