From: Lars Hjemli <hjemli@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH v4 1/2] for-each-repo: new command used for multi-repo operations
Date: Mon, 28 Jan 2013 18:11:06 +0100 [thread overview]
Message-ID: <CAFXTnz6zN0izx8S23JFww5niVD6x-r2e7TSthqZnempUrvAEWw@mail.gmail.com> (raw)
In-Reply-To: <20130128081006.GA2434@elie.Belkin>
On Mon, Jan 28, 2013 at 9:10 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>
> Lars Hjemli wrote:
>
>> [1] The 'git -a' rewrite patch shows how I think about this command -
>> it's just an option to the 'git' command, modifying the way any
>> subcommand is invoked (btw: I don't expect that patch to be applied
>> since 'git-all' was deemed to generic, so I'll just carry the patch in
>> my own tree).
>
> As one data point, 'git all' also seems too generic to me but 'git -a'
> doesn't. Intuition can be weird.
>
> So if I ran the world, then having commands
>
> git -a diff
>
> and
>
> git for-each-repo git diff
>
> do the same thing would be fine. Of course I don't run the world. ;-)
This would make me very happy. Junio?
--
larsh
next prev parent reply other threads:[~2013-01-28 17:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 12:46 [PATCH v4 0/2] for-each-repo: new command for multi-repo operations Lars Hjemli
2013-01-27 12:46 ` [PATCH v4 1/2] for-each-repo: new command used " Lars Hjemli
2013-01-27 19:04 ` Junio C Hamano
2013-01-27 19:42 ` John Keeping
2013-01-27 19:45 ` Junio C Hamano
2013-01-28 7:50 ` Lars Hjemli
2013-01-28 8:10 ` Jonathan Nieder
2013-01-28 17:11 ` Lars Hjemli [this message]
2013-01-28 18:35 ` Junio C Hamano
2013-01-28 17:45 ` Junio C Hamano
2013-01-28 18:35 ` Lars Hjemli
2013-01-28 18:51 ` Junio C Hamano
2013-01-28 19:42 ` Lars Hjemli
2013-01-28 20:12 ` Jens Lehmann
2013-01-28 20:34 ` Junio C Hamano
2013-01-28 21:25 ` Jens Lehmann
2013-02-04 6:41 ` Junio C Hamano
2013-01-27 12:46 ` [PATCH v4 2/2] git: rewrite `git -a` to become a git-for-each-repo command Lars Hjemli
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=CAFXTnz6zN0izx8S23JFww5niVD6x-r2e7TSthqZnempUrvAEWw@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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).