Thien-Thi Nguyen <[EMAIL PROTECTED]> writes: > BTW, what is the prevailing advice if i want to publish a git repo > containing only diffs between upstream gnulib my branches? The goal is > to make these branches available w/ minimal space/bandwidth cost.
Do you really need to fork gnulib to do this? Gnulib supports project-specific changes using the --local-dir parameter. Examples of a small override directory: http://git.savannah.gnu.org/gitweb/?p=gnutls.git;a=tree;f=gl/override;hb=HEAD http://git.savannah.gnu.org/gitweb/?p=libidn.git;a=tree;f=lib/gl/override/lib;hb=HEAD Examples of a large override directory: http://cvs.savannah.gnu.org/viewvc/gettext/gettext/gnulib-local/ Thus, if you want to change gnulib for just one particular project, you are better of using the up-stream gnulib and having a local --local-dir directory with your local changes. If you need the same changes in multiple projects, maybe you could set up a git project that contains those overrides? Of course, it is better to merge your changes into the real gnulib. If you've noticed a real problem, report that and it would hopefully be fixed. /Simon
