From: Jakub Narebski <jnareb@gmail.com>
To: sverre@rabbelier.nl
Cc: "Giuseppe Bilotta" <giuseppe.bilotta@gmail.com>,
git@vger.kernel.org, "Petr Baudis" <pasky@suse.cz>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH 1/2] gitweb: add patch view
Date: Sat, 29 Nov 2008 17:10:26 +0100 [thread overview]
Message-ID: <200811291710.27891.jnareb@gmail.com> (raw)
In-Reply-To: <bd6139dc0811290743s6cf8e534nddd8a09698ea22b9@mail.gmail.com>
On Sat, 29 Nov 2008, Sverre Rabbelier wrote:
> On Sat, Nov 29, 2008 at 14:41, Giuseppe Bilotta
> <giuseppe.bilotta@gmail.com> wrote:
> > Trying to use 'commitdiff_plain' output as input to git am results in
> > some annoying results such as doubled subject lines. We thus offer a new
> > 'patch' view that exposes format-patch output directly. This makes it
> > easier to offer patches by linking to gitweb repositories.
>
> If this does what I think it does I would be very happy with this
> feature :). Only yesterday I wanted to link someone to a patch I put
> up on repo.or.cz, but instead ended up telling them to download the
> snapshot.
True. 'commitdiff_plain' wasn't good enough; what's more it suffers
from the same ambiguity as 'commitdiff', i.e. it is both means to
show diff _for_ a commit (perhaps selecting one of parents), and
showing diff _between_ two commits; the new 'patch' always shows
diff for a commit, or for a series of commits.
>
> As an additional feature request; would it be possible to have a view
> that exposes a patch that is directly applyable by the patch command?
Both new 'patch' ('patchset') and old 'blobdiff_plain' should be
directly applicable by patch and by git-apply.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-11-29 16:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 13:41 [PATCH 0/2] gitweb: patch view Giuseppe Bilotta
2008-11-29 13:41 ` [PATCH 1/2] gitweb: add " Giuseppe Bilotta
2008-11-29 13:41 ` [PATCH 2/2] gitweb: links to patch action in commitdiff and shortlog view Giuseppe Bilotta
2008-11-29 15:43 ` [PATCH 1/2] gitweb: add patch view Sverre Rabbelier
2008-11-29 16:10 ` Jakub Narebski [this message]
2008-11-29 16:48 ` Giuseppe Bilotta
2008-11-29 16:50 ` Sverre Rabbelier
2008-11-30 1:06 ` [PATCH 0/2] gitweb: " Jakub Narebski
2008-11-30 1:44 ` Giuseppe Bilotta
2008-12-01 0:45 ` Jakub Narebski
2008-12-01 1:10 ` Giuseppe Bilotta
2008-12-01 11:02 ` Jakub Narebski
2008-12-03 9:25 ` Giuseppe Bilotta
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=200811291710.27891.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=giuseppe.bilotta@gmail.com \
--cc=pasky@suse.cz \
--cc=sverre@rabbelier.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.