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

Re: GitHub issue with "ignore"

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Mon, 16 Mar 2015 09:32:32 +0000

On 16 March 2015 at 06:40, Lord KiRon <lordkiron_at_gmail.com> wrote:
> Since GoogleCode are in process of being closed, I as many other users moved
> to GitHub.
>
> In general the move went swiftly but then I encountered a major issue using
> TortuiseSVN with GitHub.
>
> The problem manifest itself after you add file or folder (usually "obj" and
> "bin" folders) to ignore or recursive ignore.
> After that you can't commit (changes to) such folder.
> I am getting "Invalid PROPPATCH property" error.
>
> After some research, it looks like the problem is related to fact that
> HitHub does not support "propset .ignore" at all.
>
> As result working with TSVN becomes very inconvenient forcing me to move to
> Git or some opther tool.
> I afraid many others will have the same problem.
>
> So basically we have a several issues:
>
> 1. Not being able to ignore files (maybe can be worked around by detecting
> github and issuing gitignore?)
>
> 2. Not being able to commit at all after adding file/folder to ignore.
> (Maybe can be at least detected either somehow by protocol or at least by
> presence of "https://github.com/" and disable "ignore otion or to have a
> option in settings to disable it, in order to avoid user confusion).

I sympathise with this; I have seen the same issues in another
project. The problem is that everything to do with the working copy
and the repository is handled internally by the Subversion library.
TortoiseSVN just makes API calls to it. So to make .gitignore work you
would have to make subversion grow a new feature where it gets its
ignore list from a file. You'd need to ask for that on the subversion
mailing list.

I know github is big - probably the most popular open source code
hosting now - but it is not the only one and it would be hard to add
workarounds for svn-git, svn-mercurial, svn-perforce ... for every
alternate VCS out there.

I guess not supporting subversion properties would be common to most
svn-xxx bridges so it might be possible for TortoiseSVN to have a list
of WC folders for which properties are not supported and exclude those
options from the menus, or at least issue a warning.

Simon

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3105537

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-03-16 10:33:02 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.