* Origin URL in patch view?
@ 2014-12-28 11:45 pabs3
2014-12-28 12:15 ` john
0 siblings, 1 reply; 3+ messages in thread
From: pabs3 @ 2014-12-28 11:45 UTC (permalink / raw)
Hi,
I no longer remember enough C to implement this, but it would be great
to have the patch UI contain an Origin header with the URL to the patch.
I suggest an Origin header as the Debian patch guidelines suggest it:
http://dep.debian.net/deps/dep3/
--
bye,
pabs
http://bonedaddy.net/pabs3/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20141228/f0165e2d/attachment.asc>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Origin URL in patch view?
2014-12-28 11:45 Origin URL in patch view? pabs3
@ 2014-12-28 12:15 ` john
2014-12-28 13:52 ` pabs3
0 siblings, 1 reply; 3+ messages in thread
From: john @ 2014-12-28 12:15 UTC (permalink / raw)
On Sun, Dec 28, 2014 at 07:45:29PM +0800, Paul Wise wrote:
> I no longer remember enough C to implement this, but it would be great
> to have the patch UI contain an Origin header with the URL to the patch.
> I suggest an Origin header as the Debian patch guidelines suggest it:
>
> http://dep.debian.net/deps/dep3/
I don't think this is likely to happen because the patch view is
intended to match the output of git-format-patch(1) and it appears that
the origin is intended as a "trailer" (to use Git terminology) that
appears at the bottom of the commit message and hence modifies the
original patch.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Origin URL in patch view?
2014-12-28 12:15 ` john
@ 2014-12-28 13:52 ` pabs3
0 siblings, 0 replies; 3+ messages in thread
From: pabs3 @ 2014-12-28 13:52 UTC (permalink / raw)
On Sun, 2014-12-28 at 12:15 +0000, John Keeping wrote:
> I don't think this is likely to happen because the patch view is
> intended to match the output of git-format-patch(1) and it appears that
> the origin is intended as a "trailer" (to use Git terminology) that
> appears at the bottom of the commit message and hence modifies the
> original patch.
Origin can appear at any point in the patch headers, personally I would
recommend putting it just after the From %H... in the patch output.
--
bye,
pabs
http://bonedaddy.net/pabs3/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20141228/e869a189/attachment.asc>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-12-28 13:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-28 11:45 Origin URL in patch view? pabs3
2014-12-28 12:15 ` john
2014-12-28 13:52 ` pabs3
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).