Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Keeping up with updates to sub project #20

Open
bradical opened this Issue · 2 comments

2 participants

@bradical

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

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
Admin

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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.