[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Changes to multiple issues in subversion

From: Daniel Shahaf <danielsh_at_elego.de>
Date: Tue, 12 Jul 2011 17:26:31 +0300

This change and the next one add the "api" keyword to issues that can't
be first fixed in a patch release. (IOW, that can first be fixed in
a .0 or .0.0 release.)

Probably at least some of those are doing to be wrong or controversial
(eg, possibly the bindings issue shouldn't have been labeled) --- if any
disagreement feel free to jump in and add/remove the keyword.

I only surveyed issues in the 1.7-consider and 1.8-consider milestones.

danielsh_at_tigris.org wrote on Tue, Jul 12, 2011 at 07:16:47 -0700:
> http://subversion.tigris.org/servlets/ProjectIssues
>
> User danielsh has changed several issues in subversion
> project. Below is a list of the changed issues you are associated with:
>
> Issues: Summary:
> 3768 svn_repos_parse_fns2_t.close_revision doesn't support svn_fs_commit_txn() contract
> 3922 pass client cert as stream to auth provider
> 3925 function to determine whether a path is part of a working copy
> 2676 Add svn_path_from_user_input() to the public API.
> 3923 svn_client_proplist which allows direct queries
>
>
> Changes:
>
> Field: Value:
> Keywords api (added)
>
>
> Comments:
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=2791064
>
> To unsubscribe from this discussion, e-mail: [issues-unsubscribe_at_subversion.tigris.org].
Received on 2011-07-12 16:27:40 CEST

This is an archived mail posted to the Subversion Dev mailing list.