(
Jump to the original submission)
Wed 20 May 2015 09:57:58 AM UTC, comment #6:
Contributions on Github? Almost impossible, one can't even attach patches to bugs. This fork-and-pullrequest idea is just bonkers, raises the maintenance work and/or is a warranty for poor code. Easy reviewing/editing of patches is a key feature and Github misses it.
That said, Github is undoubtly popular and has a nice shiny GUI.
|
Tue 19 May 2015 11:12:55 PM UTC, comment #5:
And a related request - please use github for project hosting. It makes contribution much easier than with Savannah. And this item is very important if you are aiming for getting more contributors/developers to the project.
|
Thu 07 May 2015 03:58:58 PM UTC, comment #4:
"I don't think that handling branches is the most urgent
problem of the avr-libc project. If at all, it's a lack of
active developers."
If you didn't brush people off when they email you patches telling them not to email you patches, you might have more active developers.
The Linux kernel has lots of developers so Linus can afford a big ego and dismissive attitude. You... not so much.
|
Sat 02 May 2015 07:34:15 PM UTC, comment #3:
I don't think that handling branches is the most urgent
problem of the avr-libc project. If at all, it's a lack of
active developers. (Even for a DVCS, I'd much prefer
Mercurial, but that's another story.)
I wouldn't mind if someone automates a git mirror of the
repository if they feel easier about that. I don't see
that Savannah would offer that as a feature though.
|
Sat 02 May 2015 09:15:17 AM UTC, comment #2:
Yes, Git makes some things different and after using it for a while one can learn it makes these things better. One can learn that merging is evil and rebasing is a godsend. Entirely different workflow.
Admittedly, that's not exactly obvious to people who are used to an unchangeable history and have nothing but merging at hand, so they've never seen the concept of topic branches at work.
That said, avr-libc is very matured, so the number of experimental branches is low (zero?) and topic branches aren't urgent.
To the bug opener: git-svn handles a Subversion repo just like a Git repo locally and works very well, so it's entirely fine for following avr-libc and also for preparing patches for it. Something like
git svn clone http://svn.savannah.nongnu.org/svn/avr-libc
should get you started. Initially it takes a while, but after that it's a fine tool.
|
Sat 02 May 2015 07:01:42 AM UTC, comment #1:
So far, none of the avr-libc developers has ever requested
this.
Your general statement is wrong, btw: I don't like it at
all, because git makes everything different than everyone
else.
|
Sat 02 May 2015 06:16:01 AM UTC, original submission:
Git is kinda the standard for version control now. Developers like it very much. Pweety pwease.
|
(Note: upload size limit is set to 16384 kB, after insertion of the required
escape characters.)
Attach File(s):
Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Follow 3 latest changes.