On Mon, Feb 18, 2013 at 8:20 PM, <gree...@obbligato.org> wrote: > Paul Campbell <pcampb...@kemitix.net> writes: > >> Subsequent git subtree push/pull operations now default to the values >> stored in .gitsubtree, unless overridden from the command line. >> >> The .gitsubtree file should be tracked as part of the repo as it >> describes where parts of the tree came from and can be used to update >> to/from that source. > > I agree with the basic idea but have some questions about the > implementation. > > Is there precedent of git commands storing information in hidden files > and requiring those files to be added to the repository and tracked? It > seems like a bit of a kludge. > > Could we use notes or something for this? > > I'm not necessarily against the patches, I just want to make sure we > don't go down a road that won't be acceptable later on. > > -David
I'm not familiar with git notes. Adding that the my to-read list. I took my inspiration from git submodules which uses the .gitmodules file for a similar purpose. -- Paul [W] Campbell -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
