From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
git@vger.kernel.org, cmn@elego.de
Subject: Re: [PATCH v2 1/2] check-ref-format --print: Normalize refnames that start with slashes
Date: Mon, 29 Aug 2011 15:01:18 -0400 [thread overview]
Message-ID: <20110829190118.GE756@sigill.intra.peff.net> (raw)
In-Reply-To: <20110829185011.GC756@sigill.intra.peff.net>
On Mon, Aug 29, 2011 at 02:50:12PM -0400, Jeff King wrote:
> 3. Having better tool support for comparing two sets of commits. The
> ideal interface (to me) for this workflow would be something like:
BTW, this discussion is obviously about comparing what was applied
upstream with what was submitted, but I think such a tool could have
other purposes, too. It should be able to provide a much nicer interdiff
between two versions of the same series (e.g., for reviewers looking at
a re-roll). You could even use it as maintainer to apply a re-roll,
giving you a chance to review the differences as you apply.
-Peff
next prev parent reply other threads:[~2011-08-29 19:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 4:12 [PATCH v2 0/2] Fix reference name format check and normalization Michael Haggerty
2011-08-27 4:12 ` [PATCH v2 1/2] check-ref-format --print: Normalize refnames that start with slashes Michael Haggerty
2011-08-27 4:22 ` Michael Haggerty
2011-08-27 18:30 ` Junio C Hamano
2011-08-28 15:50 ` git project patch workflow Michael Haggerty
2011-08-29 18:50 ` [PATCH v2 1/2] check-ref-format --print: Normalize refnames that start with slashes Jeff King
2011-08-29 19:01 ` Jeff King [this message]
2011-08-29 20:56 ` Junio C Hamano
2011-08-29 21:27 ` Jeff King
2011-08-29 19:57 ` Johannes Sixt
2011-08-29 20:02 ` Jeff King
2011-08-29 22:22 ` Junio C Hamano
2011-08-27 4:12 ` [PATCH v2 2/2] Forbid DEL characters in reference names Michael Haggerty
2011-08-27 18:40 ` 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=20110829190118.GE756@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
/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).