List for cgit developers and users
 help / color / mirror / Atom feed
From: john at keeping.me.uk (John Keeping)
Subject: odd patch issue
Date: Mon, 14 Mar 2016 21:20:37 +0000	[thread overview]
Message-ID: <20160314212037.GA20327@serenity.lan> (raw)
In-Reply-To: <20160314134629.63b858f5@sheelba.scrye.com>

On Mon, Mar 14, 2016 at 01:46:29PM -0600, Kevin Fenzi wrote:
> We are seeing an odd behavior with diffs/patches here. I think it's a
> bug, but perhaps we are doing something wrong. ;) 
> 
> If you look at: 
> 
> https://fedorapeople.org/cgit/adelton/public_git/CGI-sessions.git/diff/app.cgi?id=additional-attributes
> 
> you can see just the diff for that one file. 
> However, if you try and get a patch for just that one file: 
> 
> https://fedorapeople.org/cgit/adelton/public_git/CGI-sessions.git/patch/app.cgi?id=additional-attributes
> 
> You get also any other files affected in that patch. (ie, not just
> app.cgi). Is this expected? or a bug?

I think this is expected.  It doesn't really make sense for "patch" to
use a path since it includes the header and commit message, so it
doesn't take a path argument.  (Hopefully you created that URL manually
and didn't follow a link - if we generate such a link that is a bug.)

If you want a diff without all the HTML markup you can use "rawdiff":

	https://fedorapeople.org/cgit/adelton/public_git/CGI-sessions.git/rawdiff/app.cgi?id=additional-attributes


  reply	other threads:[~2016-03-14 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 19:46 kevin
2016-03-14 21:20 ` john [this message]
2016-03-14 21:44   ` kevin
2016-03-14 22:44     ` john
2016-03-16 18:43       ` kevin

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=20160314212037.GA20327@serenity.lan \
    --to=cgit@lists.zx2c4.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).