From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Jean-Marie Lemetayer <jeanmarie.lemetayer@gmail.com>,
git@vger.kernel.org
Subject: Re: [RFC] new subcommand: git sync
Date: Fri, 26 Feb 2021 15:20:34 -0800 [thread overview]
Message-ID: <xmqqlfbaquv1.fsf@gitster.g> (raw)
In-Reply-To: <xmqq35xisbp3.fsf@gitster.g> (Junio C. Hamano's message of "Fri, 26 Feb 2021 14:31:36 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> so that you can prepare
> ...
> beforehand and then eval the output from the script you wrote with
> "git for-each-ref".
Ehhh, not "eval the output from the script", but "eval the script".
In essense, you use "for-each-ref --format" as a tool to write a
script, and then execute it.
prev parent reply other threads:[~2021-02-26 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 9:08 [RFC] new subcommand: git sync Jean-Marie Lemetayer
2021-02-26 15:25 ` Ævar Arnfjörð Bjarmason
2021-02-26 16:42 ` Randall S. Becker
2021-03-01 9:48 ` Jean-Marie Lemetayer
2021-03-01 13:55 ` Randall S. Becker
2021-02-26 22:31 ` Junio C Hamano
2021-02-26 23:20 ` Junio C Hamano [this message]
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=xmqqlfbaquv1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jeanmarie.lemetayer@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).