On Nov 17, 9:00 pm, Paul Miller <jett...@gmail.com> wrote:
> On Nov 17, 4:37 pm, trans <transf...@gmail.com> wrote:
>
> > (Quite honestly, if it wasn't for grancher I would not be using
> > github's website features at all, and I may not have even bothered
> > switching to github b/c of it). Unfortunately, grancher does not work
> > on Ruby 1.9+ yet and the author seems to have forgotten about it :-(
>
> I wonder if you could checkout the other branch as a submodule or
> something.  Can that actually be done?  I also wonder why the separate
> branch offends you so much that you can't use the service because of
> the
> way its shaped.  Oh noes, it's not how I would have done it, so I
> can't use
> it at all.  Really?

If it wasn't for grancher (or something like it) I would not have been
able to generate my site files as I do and git them into the gh-pages
branch. In other words, I would have to have written grancher myself
if it didn't already exist, and really I have enough to do, so without
it I would have been content to stick with my old system of rsyncing
the site to rubyforge, et al.

> Personally, I like the way it works now.  Why on earth would you want
> to
> pollute your dev files with generated html and/or website content?
> For
> pages with binary files, I find I'm frequently tempted wreck the
> history
> and do a force push to save some space.  That'd be pretty irritating
> for
> people that already pulled it if it was sitting in the HEAD, ya know?

Why do you see it as pollution? The site is an important part of the
project. How often would you be committing the site files anyway? I
basically do it ounce per new release tag. That's it. As it stands,
the site files are already being tracked, just in a different branch.
So why is it such a big deal to track them along with the dev files?

> So, if the sub directory thing is ever actually implemented, I hope
> they
> leave the gh-pages method alone.  It's better.

To each his own. I'm fine with support for both approaches.

-- 
You received this message because you are subscribed to the Google Groups 
"GitHub" group.
To post to this group, send email to git...@googlegroups.com.
To unsubscribe from this group, send email to 
github+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/github?hl=en.

Reply via email to