I see, tnx for the pointer.
Would inclusion of this patch be viable option then?
Patch below, it is possible to look at it here to:
Patch:
https://github.com/teonsystems/git/commit/27449825ff4d7bb3eecb5a3e32692aaf1ab1a026
Branch:
https://github.com/teonsystems/git/commits/feature/configurable
On Tue, Sep 2, 2014 at 3:30 AM, Bostjan Skufca wrote:
> There is currently no way to transfer/share repository configuration
> between clones.
See http://article.gmane.org/gmane.comp.version-control.git/216624
--
Duy
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body o
I see another crux of the problem.
There is currently no way to transfer/share repository configuration
between clones.
(Or is there? Could this be done with attributes? Probably not...)
This is a bit awkward.
Are there any plans to provide such functionality? Pros/cons?
(It should be limited in
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 b
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 curr
Hi there,
I created a patch which makes ".gitignore" filename configurabe.
Preliminary diff is pasted below.
My question is:
Would something like this be acceptable for inclusion?
(providing documentation and test cases will be done too, of course)
See "Motivation" part below for additional expl
6 matches
Mail list logo
