Re: Confusing svn_log_entry_t docstrings.

2010-08-13 Thread C. Michael Pilato
On 08/13/2010 01:04 PM, Bert Huijben wrote: > > svn_log_changed_path2_t is defined as a structure starting with the exact > same definition as svn_log_changed_path_t. So any svn_log_changed_path2_t > instance can be seen as a svn_log_changed_path_t, but you miss some > fields that way. > > The pr

RE: Confusing svn_log_entry_t docstrings.

2010-08-13 Thread Bert Huijben
> -Original Message- > From: C. Michael Pilato [mailto:cmpil...@collab.net] > Sent: vrijdag 13 augustus 2010 18:40 > To: Subversion Development > Subject: Confusing svn_log_entry_t docstrings. > > Can someone help me make sense of some of our public docstrings?

Confusing svn_log_entry_t docstrings.

2010-08-13 Thread C. Michael Pilato
Can someone help me make sense of some of our public docstrings? I'm looking at the svn_log_entry_t structure, and I see the following: typedef struct svn_log_entry_t { /** A hash containing as keys every path committed in @a revision; the * values are (#svn_log_changed_path_t *) stuctures.