search

qrush / sub

a delicious way to organize programs
http://37signals.com/svn/posts/3264-automating-with-convention-introducing-sub
MIT License
1.74k stars 148 forks source link

Keeping up with updates to sub project #20

Open bradical opened 11 years ago

bradical commented 11 years ago

I know the instructions say to run prepare.sh and then blow away the repo history and start fresh when initializing your own sub.

Would it make sense to:

  1. run prepare.sh
  2. Un-delete all of the sub-* files.
  3. maintain the git history
  4. keep a remote pointed to this project so be able to pull in the latest changes and potentially apply them to my own sub-command's scripts

Is there any easier way to do this that I'm not considering?

Thanks!

bradical commented 11 years ago

Btw, I realize this is not exactly an issue. If there is a different forum to discuss questions like this (e.g. mailing list, google group), please let me know.

qrush commented 11 years ago

Yeah, I haven't really considered this. We could take a github pages/gh-pages branch approach and start a new git history. No matter what since we encourage renaming right now, it's going to be a real PITA to merge no matter what way we go about this.

Also re: discussion, this is a fine place. Last thing I need is another Google Group to maintain :)

markstos commented 1 year ago

The sub project is so stable I don't think it's a big issue to manually patch your generated code if there's an issue that affects you. (For example, there have been few changes over the past 10 years...). Given the lack of interest in this feature over the past decade, I think this issue just be closed.