Hi Jonathan, nope, haven't seen zit before, it does partly what I would need, but just for one file at a time (a "bit" awkward) and not really portable (git clone will not clone .FILE.git/exclude, for example).
Anyway, do you think that a patch which makes .gitignore filename configurable would be appropriate for inclusion in future git releases? b. On 30 August 2014 07:43, Jonathan Nieder <[email protected]> wrote: > Hi, > > Bostjan Skufca wrote: > >> Git is great for tracking code development, but when deploying >> mentioned code by using git itself, various configuration files must >> be created additionally, which are normally .gitignored, for various >> reasons (code portability, sensitive data, etc). There is currently no >> simple way of tracking changes to those critical configuration files >> (at least none that I am aware of). >> >> One way to approach this would be tracking those changes in separate >> git repository. > > Have you seen zit > <https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools#Zit>? > > Curious, > Jonathan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
