[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: where do folks push scrath branches for kate?
From:       Matthew Woehlke <matthew.woehlke () kitware ! com>
Date:       2013-12-26 23:30:42
Message-ID: l9ie6m$rus$1 () ger ! gmane ! org
[Download RAW message or body]

On 2013-12-26 15:20, Matthew Woehlke wrote:
> I would like to push a kate branch somewhere, for two reasons:
>
> 1. People can look at the commits before a merge.
>
> 2. I can generate "better" review requests that way.
>
> However, I also may need to force-push the branch, and *definitely* want
> to be able to delete it once it is either merged or abandoned. For this
> reason, the "primary" repository is apparently "out". I also can't use a
> scratch repo because it rejects pushing the existing history.
>
>
> I am wondering, do other people push personal/scratch/temporary kate
> branches somewhere, and if so, where?
>
> Suggestions welcomed...

FTR, here's a reply from Ben (sysadmin):

> Please note that git.kde.org also offers clone repositories, which
> can be created by running the following command:
>
> ssh git@git.kde.org clone $repoName $cloneName
>
> This will result in a repository being created at
> clones/$repoName/$username/$cloneName. Both clone and scratch
> repositories [...] can be freely force pushed. The clone repository
> mechanism exists to workaround the issue with audit errors you
> found.

...so that seems to be the recommended action. (This worked for me where 
the scratch repo didn't. Apparently I need to read through the entire 
page...)

-- 
Matthew

_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]