[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: dist-git proof of concept phase 1 complete



On Wed, Dec 16, 2009 at 10:42:28AM -0500, Simo Sorce wrote:
> On Wed, 2009-12-16 at 07:28 -0800, Toshio Kuratomi wrote:
> > On Wed, Dec 16, 2009 at 12:33:20AM -0500, Jon Masters wrote:
> > > On Tue, 2009-12-15 at 12:35 -0800, Toshio Kuratomi wrote:
> > > 
> > > > master makes a lot of sense from a git perspective.  devel (or rawhide)
> > > > makes sense from what we actually call the code that that branch eventually
> > > > makes.  A symlink might alleviate the confusion but it could also add to it.
> > > > (For instance, I was operating in the kernel/devel branch but when I want to
> > > > git checkout -b devel git gives me a strange error.)
> > > > 
> > > > I don't see a clear answer for what's best here, yet. :-(
> > > 
> > > I think those of us who follow rawhide will quickly realize the change
> > > in naming (ok maybe a symbol is vaguely useful, and also needs to be
> > > explained somewhere when people inevitably ask) and move on. Conversely,
> > > someone who is new or hasn't followed "devel" branches before should
> > > just be able to use git how they have elsewhere and it should work.
> > > 
> > > Summary: easier to make life easier for new developers.
> > > 
> > Not all packagers use git elsewhere.
> 
> But for anyone that does not using "master" as the default branch will
> be a problem. If you never used git you have to learn a lot of things
> anyway.
> 
Yeah, not disagreeing with this at all.  Just disagreeing with the idea that
following the git conventions is a no brainer that's going to be intuitive
to everyone.

-Toshio

Attachment: pgpy2d85mSvmw.pgp
Description: PGP signature


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]