[Kde-scm-interest] Project release tags on Gitorious

[Thomas Zander]

On Tuesday 1. December 2009 01.08.46 Michael Jansen wrote:
> On Monday 30 November 2009 15:59:16 Eike Hein wrote:
> > On 11/30/2009 01:27 AM, Michael Jansen wrote:
> > > This is btw one of the things i really don't like about the git move. I
> > > use git-svn locally and prefer git to svn usage wise. But having to put
> > > up with cloning a myriad of repositories on gitorious, keeping them up
> > > to date which means uploading all that stuff i just downloaded to just
> > > commit a small one line fix in a build script is something i don't
> > > really look forward too.
> >
> > Hmm. SVN won't let you commit on an outdated working copy
> > either (and git imho makes it much easier to get it upda-
> > ted again), and you don't have to upload *all* you down-
> > loaded to make a commit ...
> 
> Downloading is faster.
> 
> And i have top upload the changes in git. Try to push to a qt clone on
>  gitorious you haven't used for 3 month. And so the *know it all's* won't
>  bother me. Imagine you still have a open merge request so you can't delete
>  and recreate the repository.
> 
> You will sit there while git upload 3 month of qt development unrelated to
>  you triny fix to your clone.

This only happens if you merge your topic branch with master before making a 
merge request.
Not sure if you should do that anyway. In practice I don't think you'll have 
to see this problem.

There is an open feature request on gitorious to fix this issue, btw. (with a 
proposed solution) So, yes, the general problem is known and should be looked 
at.
-- 
Thomas Zander