It needs to be a full SHA1 (use git diff --full-index if you're generating
a diff for Review Board, or use our post-review tool instead), and needs to
use ?id= and not ?id2=
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Jun 13, 2012 at 12:10 AM, Ryan Raasch <ryan.raa...@gmail.com> wrote:
> Ok. I have been investigating this... This is one difficult setup...
> Cgit seems to be sending the newest version of the blob file per default.
> It doesn't
> seem to be sending the blob specified in the url.
> Using the newest commit from the cgit respository...
> Get the two indices in the commit patch.
> curl http://hjemli.net/git/cgit/blob/cgit.css?id2=e06c261 > file1
> curl http://hjemli.net/git/cgit/blob/cgit.css?id2=651a320 > file2
> These two files are identical! Why? Am I using the wrong command for cgit?
> This is the issue from my previous post involving previous applied
> patches. I am
> trying to dig through the cgit code also to find what I am doing wrong.
> Any suggestions, please :) ?
> On Tuesday, June 12, 2012 3:44:29 PM UTC+2, Ryan Raasch wrote:
>> I am having problems with patches that are already in the repository. The
>> cannot be seen because the patch fails to apply.
>> Reversed (or previously applied) patch detected! Assume -R? [n]
>> Apply anyway? [n]
>> Skipping patch.
>> 3 out of 3 hunks ignored -- saving rejects to file
>> It is quite easy to provoke (using the cgit interface) by just uploading
>> a request that already exists in the git repository. Am I doing something
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at