From: Mitar <mmitar@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Seth Robertson <in-gitvger@baka.org>, git@vger.kernel.org
Subject: Re: post-fetch, tweak-fetch hook
Date: Mon, 7 May 2012 11:11:30 +0200 [thread overview]
Message-ID: <CAKLmikNuUB01xKSm9Skd2chXWw3BcWDHT23hqWtNBJPJfYqDKQ@mail.gmail.com> (raw)
In-Reply-To: <20120507072934.GC19874@sigill.intra.peff.net>
Hi!
On Mon, May 7, 2012 at 9:29 AM, Jeff King <peff@peff.net> wrote:
> I would say the "most git" thing would be to implement "fetch
> --porcelain", and use its output.
Yes, that would be also useful. It still makes two different
interfaces for probably same post-processing (after push and after
fetch), but still better than nothing, what is current state.
Mitar
next prev parent reply other threads:[~2012-05-07 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 20:52 post-fetch, tweak-fetch hook Mitar
2012-05-06 23:10 ` Seth Robertson
2012-05-06 23:54 ` Mitar
2012-05-07 7:29 ` Jeff King
2012-05-07 9:11 ` Mitar [this message]
2012-05-07 13:38 ` Jeff King
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=CAKLmikNuUB01xKSm9Skd2chXWw3BcWDHT23hqWtNBJPJfYqDKQ@mail.gmail.com \
--to=mmitar@gmail.com \
--cc=git@vger.kernel.org \
--cc=in-gitvger@baka.org \
--cc=peff@peff.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 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).