On 09/20/13 01:38, Paul Davis wrote:
> it is also much easier for project maintainers to handle pull requests than
> simple patches, which means that someone having their own fork on github
> can actually be doing the project a service, rather than seeking to "split"
> from it.
i'm aware of that feature of github and i'm using it myself in both
directions.
nevertheless, personally i only ever "github fork" a project after i
pulled a clone of the original project to my desktop, worked on it and
eventually want to submit a pull request.
git makes it so easy to handle multiple repositories simultaneously
(most of my git project have 2-4 remotes) and/or to change the URL of a
single remote.
nevertheless, it's not very important - i only found it slightly strange.
fgamsdr
IOhannes
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev
This archive was generated by hypermail 2.1.8 : Sat Sep 21 2013 - 00:15:04 EEST