On Tue, Jul 07, 2020 at 09:44:47PM +0200, Markus Larsson wrote:
>
>
> On 7 July 2020 21:20:22 CEST, Matthew Miller wrote:
> >On Tue, Jul 07, 2020 at 09:03:19PM +0200, Till Maas wrote:
> >> in https://pagure.io/fesco/issue/2410 I proposed to name the dist-git
> >> branch for Fedora Rawhide "rawhi
On Wed, Jul 08, 2020 at 11:31:20AM -0400, Matthew Miller wrote:
> On Wed, Jul 08, 2020 at 03:48:23PM +0200, Till Maas wrote:
> > Just had another idea, how about instead of branch down from the rawhide
> > branch to new branched to make Rawhide always use the fxy version that
> > it develops. So in
On Wed, Jul 08, 2020 at 03:48:23PM +0200, Till Maas wrote:
> Just had another idea, how about instead of branch down from the rawhide
> branch to new branched to make Rawhide always use the fxy version that
> it develops. So instead of creating branched f33 later we would rename
> master to f33 now
On 08.07.2020 16:29, Pierre-Yves Chibon wrote:
> One wonder which I have is: should we keep a "master" branch, just as a
> symlink
> to the "rawhide" one for backward compatibility purposes?
Yes. Master branch is hardcoded in lots of places (infra, maintainer's
scripts, etc.) and such rename will
On Wednesday, 08 July 2020 at 16:29, Pierre-Yves Chibon wrote:
> On Wed, Jul 08, 2020 at 10:09:35AM -0400, Kaleb Keithley wrote:
> >Whatever name is picked: devel, main, rawhide, next, etc., how about
> >setting the default branch.
> >E.g. `git symbolic-ref HEAD refs/heads/rawhide`
> >
On Wed, Jul 08, 2020 at 10:09:35AM -0400, Kaleb Keithley wrote:
>Whatever name is picked: devel, main, rawhide, next, etc., how about
>setting the default branch.
>E.g. `git symbolic-ref HEAD refs/heads/rawhide`
>This way when someone clones the repo they don't need to know or reme
Whatever name is picked: devel, main, rawhide, next, etc., how about
setting the default branch.
E.g. `git symbolic-ref HEAD refs/heads/rawhide`
This way when someone clones the repo they don't need to know or remember
which name Fedora is using as the mainline development branch.
On Wed, Jul
On 08. 07. 20 15:48, Till Maas wrote:
On Tue, Jul 07, 2020 at 09:03:19PM +0200, Till Maas wrote:
Hi,
in https://pagure.io/fesco/issue/2410 I proposed to name the dist-git
branch for Fedora Rawhide "rawhide" to clarify the purpose of that
branch. There was also some feedback that Rawhide might n
On Tue, Jul 07, 2020 at 09:03:19PM +0200, Till Maas wrote:
> Hi,
>
> in https://pagure.io/fesco/issue/2410 I proposed to name the dist-git
> branch for Fedora Rawhide "rawhide" to clarify the purpose of that
> branch. There was also some feedback that Rawhide might not be the best
> name and it co
On Tue, Jul 07, 2020 at 10:13:36PM +, Gary Buhrmaster wrote:
> I (strongly) support the renaming of the branch, but I really
> really would prefer there to be a rough consensus on the
> replacement name across the entire git community, so
> that I don't need to remember to git-checkout devel i
On Tue, Jul 7, 2020 at 7:04 PM Till Maas wrote:
>
> Hi,
>
> in https://pagure.io/fesco/issue/2410 I proposed to name the dist-git
> branch for Fedora Rawhide "rawhide" to clarify the purpose of that
> branch. There was also some feedback that Rawhide might not be the best
> name and it could be re
On 7 July 2020 21:20:22 CEST, Matthew Miller wrote:
>On Tue, Jul 07, 2020 at 09:03:19PM +0200, Till Maas wrote:
>> in https://pagure.io/fesco/issue/2410 I proposed to name the dist-git
>> branch for Fedora Rawhide "rawhide" to clarify the purpose of that
>> branch. There was also some feedback t
On Tue, Jul 07, 2020 at 09:03:19PM +0200, Till Maas wrote:
> in https://pagure.io/fesco/issue/2410 I proposed to name the dist-git
> branch for Fedora Rawhide "rawhide" to clarify the purpose of that
> branch. There was also some feedback that Rawhide might not be the best
> name and it could be re
13 matches
Mail list logo
