On Tue, Dec 8, 2015 at 3:15 PM, Sam Ruby <[email protected]> wrote:
> On Tue, Dec 8, 2015 at 1:06 PM, sebb <[email protected]> wrote:
>> On 8 December 2015 at 15:50, Sam Ruby <[email protected]> wrote:
>>> On Tue, Dec 8, 2015 at 9:20 AM, Jim Jagielski <[email protected]> wrote:
>>>>
>>>>> On Dec 5, 2015, at 5:21 PM, sebb <[email protected]> wrote:
>>>>>
>>>>> On 5 December 2015 at 02:21, Sam Ruby <[email protected]> wrote:
>>>>>> Repository:
>>>>>>
>>>>>> https://github.com/apache/whimsy
>>>>>
>>>>> The SVN repo is still present at
>>>>>
>>>>> https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy
>>>>>
>>>>> Is that going to disappear, or can we still udpate that?
>>>
>>> That copy is now out of date.
>>>
>>>> PLEASE KEEP!! I don't want to be forced to use git. The whole idea
>>>> is to make it easy for developers, right? And there are a bunch
>>>> that are comfortable w/ svn.
>>>>
>>>> If we provide git functionality for svn-based projects, we should
>>>> also provide svn access for git-based ones.
>>>
>>> GitHub provides svn access[1].  Try it out:
>>>
>>> svn checkout https://github.com/apache/whimsy
>>
>> Just checked - seems it's read-only.
>
> Should be read/write since May of 2010:
>
> https://github.com/blog/644-subversion-write-support
> https://github.com/blog/1178-collaborating-on-github-with-subversion
>
> I note that:
>
> 1) you are not listed as a committer in LDAP for whimsy
>
> 2) you have not associated your githubUsername with your ASF account;
> that would be done using https://matt.apache.org/

I've now successfully made a commit using the svn interface:

https://github.com/apache/whimsy/commit/efa7ffbba86b9d6e4b497f7c3f7a8e35d32dc346

Notes: an access token is required:

https://help.github.com/articles/creating-an-access-token-for-command-line-use/

You may want to configure how svn stores your credentials:

http://svnbook.red-bean.com/en/1.7/svn.serverconfig.netmodel.html#svn.serverconfig.netmodel.creds

- Sam Ruby

>>> [1] https://github.com/blog/626-announcing-svn-support

Reply via email to