From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
git@vger.kernel.org, Jeff King <peff@peff.net>,
Elijah Newren <newren@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: [PATCH 2/3] fast-export: add new --refspec option
Date: Fri, 10 May 2013 08:42:37 +0200 [thread overview]
Message-ID: <518C96DD.50304@viscovery.net> (raw)
In-Reply-To: <7vk3n763is.fsf@alter.siamese.dyndns.org>
Am 5/10/2013 3:13, schrieb Junio C Hamano:
> * On the other hand, "git log 'fc/*'" might be a handy thing for
> any command that wants to have multiple starting points for
> revision traversal, so in principle I would not mind such an
> enhancement to rev-list machinery.
Currently, we spell this as "git log --branches=fc" or
"git log --branches='*export*'". But I do not mean to say that
"git log fc/\*" would be a bad thing to have.
-- Hannes
next prev parent reply other threads:[~2013-05-10 6:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 1:31 [PATCH 0/3] Support for old:new remote-helper push Felipe Contreras
2013-05-09 1:31 ` [PATCH 1/3] fast-export: improve argument parsing Felipe Contreras
2013-05-09 22:17 ` Junio C Hamano
2013-05-09 23:02 ` Felipe Contreras
2013-05-09 23:27 ` Junio C Hamano
2013-05-09 23:33 ` Felipe Contreras
2013-05-10 4:49 ` Junio C Hamano
2013-05-09 1:31 ` [PATCH 2/3] fast-export: add new --refspec option Felipe Contreras
2013-05-09 22:32 ` Junio C Hamano
2013-05-09 22:53 ` Felipe Contreras
2013-05-09 23:23 ` Junio C Hamano
2013-05-09 23:32 ` Felipe Contreras
2013-05-10 0:21 ` Junio C Hamano
2013-05-10 0:44 ` Felipe Contreras
2013-05-10 1:13 ` Junio C Hamano
2013-05-10 6:42 ` Johannes Sixt [this message]
2013-05-16 9:15 ` Felipe Contreras
2013-05-09 1:31 ` [PATCH 3/3] transport-helper: add support for old:new refspec Felipe Contreras
2013-05-16 9:15 ` [PATCH 0/3] Support for old:new remote-helper push Felipe Contreras
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=518C96DD.50304@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
--cc=srabbelier@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;
as well as URLs for NNTP newsgroup(s).