The demo server does point to the active SVN server. This is okay
because review board never does any commits to version control.

-David

On Tue, Feb 17, 2009 at 11:17 AM, Anthony Foglia <afog...@princeton.com> wrote:
>
> Thanks.  I was aware of the tool, but not using it.  My questions are
> more about how to use the demo, than review board.
>
> What repository should be used for demo users: Navi or Review Board SVN?
>  From where do I check out the repository so I can make changes to post
> for demo purposes?
>
> I am assuming the demo does not use the Google Code SVN server where the
> review board code is, because that would risk demo users making changes
> to the published code.  Am I wrong?  Is there simply a directory that's
> a sandbox for demo users?  If so, which.
>
>
> Jeff Andros wrote:
>> sorry, just hit me just how unhelpful that really was.
>>
>> There's a command line tool called post-review you can download to
>> actually produce your uploads.
>>
>> doc on the tool is here:
>> http://code.google.com/docreader/#p=reviewboard&s=reviewboard&t=Using_PostReview
>>
>> the tool can be downloaded out of svn here:
>> http://reviewboard.googlecode.com/svn/trunk/reviewboard/contrib/tools/
>>
>> 2009/2/17 Jeff Andros <j...@bigredtj.com>:
>>> diff headers for reviewboard are a bit different... the server needs
>>> to know not only the path to the file, but also the revision it was
>>> generated from... that's how it looks up the base code.  as I
>>> understand it, svn diff might give you the right headers, but I'm not
>>> sure... we use p4.
>>>
>>> 2009/2/17 Anthony Foglia <afog...@princeton.com>:
>>>> This might be a stupid question.  I'd like to play around with the
>>>> demo, and follow a patch through the review process, but I'm having
>>>> trouble uploading a patch.  My plan was just to add a file, maybe add
>>>> additional patches to it, etc.
>>>>
>>>> My first question: Which repository do I use for demo purposes?  Navi
>>>> or Review Board SVN?
>>>>
>>>> Second: What should my patch contain?  I tried making a patch with a
>>>> new file, setting the base diff path to /, but I get an "Unable to
>>>> parse diff revision header" when uploading the diff.  I think this is
>>>> because my diff was made outside any version control, and the revision
>>>> header is a timestamp.
>>>>
>>>> Do I need to check out the demo's repository first?  If so, where is
>>>> it?
>
>
>
> --
> Anthony Foglia
> Princeton Consultants
> (609) 987-8787 x233
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to