On Sun, Sep 21, 2008 at 2:36 AM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> Aaron Wagner wrote:
> > Hello,
> >
> > I'm not sure if this is expected behavior, but I just found out that
> > you can drag-n-drop items onto the repo-browser from windows explorer
> > and it will prompt you for a commit message. Neat!
> >
> > But the dialog doesn't tell you what files it will commit and I
> > found out after the fact that it did not honor my global ignore
> > settings. That was a bummer.
> >
> > So my question is if this is expected or is it a possible bug?
>
> This is expected. We had it once honor the global ignore settings, but
> that's not what people expected when dropping files/folders onto the
> repository browser.
wtf... people complained that the 'global ignores' were doing their job when
you tried to commit stuff.... sigh...
> Also, the way I personally use this is after I tag a release, I drop the
> binaries and debug symbols into that release tag (because I tag the
> release, then export that release tag and do a clean build, so I have to
> add the binaries *after* the tagging). And since I have all binary
> extensions in my global ignore pattern, that would be not what I want.
I rather like (and expected) the other behaviour. is there some 'middle
ground' we can come too.
if people expect that if you drag | drop stuff onto a repository browser it
commits everything (ignoring global-ignores) yet if you commit from your
working copy it 'honors' your global-ignores why not allow both.
say for example the commit dialogue also listed items in your global ignore
list - maybe list them in a 'grey' color (i think you use the disabled
window color i am not sure). mabye put them into a collapsable ui (ie the ui
you use for a change-list) clerly label them as 'filtered by your global
ignore settings' so people can identify them as not one of their actual
change-lists.
what do you think ?
Received on 2008-09-22 08:42:33 CEST