[Mono-dev] The new world of Git -- what else can we change :-)
apenwarr at gmail.com
Thu Jul 29 01:20:13 EDT 2010
On Thu, Jul 29, 2010 at 1:07 AM, Jon Frisby <jfrisby at mrjoy.com> wrote:
> On Jul 28, 2010, at 11:21 PM, Avery Pennarun wrote:
>> Hmm, if it's only a branch that you're working on - which is implied
>> by the jfrisby/ prefix - then I don't see any reason to put it in the
>> shared repo. That's exactly why github has a jfrisby/mono repo.
>> If you expect *other* people to be pushing to jfrisby/* branches,
>> well, that's just crazy and perhaps you shouldn't be naming them with
>> your username like that :)
> You have a good point there...
> I had envisioned a scenario wherein an individual is doing something 'important'
> as a project -- important enough to beg collaboration, but transient enough to
> not qualify for any sort of 'official' status yet.
> Of course the collaboration could happen entirely via github.com/jfrisby/mono.git
> too so perhaps this is just some SVN-induced brain-rot seeping through in my ideas. :)
I think before there was github, it was pretty common (and mostly
harmless) for people to put username/* branches into the shared repo
so they wouldn't get lost. Certainly we do this at some of our
internal-only servers at work. In theory, someone other than jfrisby
could push to a jfrisby/* branch, but in practice that never actually
With github, I think they just cleaned up the model a bit so you now
have a guarantee that nobody but jfrisby is messing with the jfrisby
repo. I doubt it affects collaboration that much; if I download the
mono/mono repo, I'm probably not going to go digging around in the
sub-branches anyway unless I'm specifically directed to.
More information about the Mono-devel-list