Re: [PATCH 1/4] contrib/subtree: Store subtree sources in .gitsubtree and use for push/pull
- From
Paul Campbell <pcampbell@kemitix.net>
- Date
- Feb 18, 2013, 20:50 UTC
- Message-ID
- <CALeLG_mfYwVow-A=10kXKHWn7HO311yy5smRcFY6Gx5W3qNDdg@mail.gmail.com>
- In-Reply-To
- <87bobh4bmz.fsf@waller.obbligato.org>
On Mon, Feb 18, 2013 at 8:20 PM, <greened@obbligato.org> wrote:
Show 22 quoted lines
> Paul Campbell <pcampbell@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