>There was no 'bug' either. It's just the way it is ;-)
Sure !
r git directory copied in every git directory that is created should
you decide to put your template directory under version control. Plus, it
might be used as a feature by people who would want to exclude some
files.
Signed-off-by: Grégoire Paris
---
Here is a better version.
Documentatio
-The template directory contains files and directories that will be copied to
-the `$GIT_DIR` after it is created.
+The template directory contains files and directories whose name do not start
+with a dot will be copied to the `$GIT_DIR` after it is created.
The template directory will
> Thanks for your guidance. I believe I just sent the patch to the
mailing list.
I just retried with the Gmail SMTP, and now I am sure it worked. Sorry
for the noobery.
r git directory copied in every git directory that is created should
you decide to put your template directory under version control. Plus, it
might be used as a feature by people who would want to exclude some
files.
Signed-off-by: Grégoire Paris
---
I hope I'm getting it right, this is my
Thanks for your guidance. I believe I just sent the patch to the mailing
list.
Le 17/02/2017 à 23:39, Philip Oakley a écrit :
From: "Grégoire PARIS"
> You could, for example, have your template directory itself be a git
repository.
I can and I do and indeed, that might be the reason behind this.
I made a PR to document this : https://github.com/git/git/pu
> I do not think we should change the behaviour
> to copy files whose names begin with a dot.
So bug turned feature it is :)
I amended my commit message accordingly.
In my case, my template dir is not at the root of the repository where
it is versioned, so it would not be a problem for me, but
> You could, for example, have your template directory itself be a git
repository.
I can and I do and indeed, that might be the reason behind this.
I made a PR to document this : https://github.com/git/git/pull/325
--
greg0ire
Le 03/03/2016 23:55, Junio C Hamano a écrit :
Grégoire PARIS writes:
Not sure how cherry-picking is managed, and whether commit is able to
see that we are doing a cherry-pick, and end it up properly. Anyway,
with Kevin's patch, we should be able to happily use cherry-pick
[Please do no
Not sure how cherry-picking is managed, and whether commit is able to
see that we are doing a cherry-pick, and end it up properly. Anyway,
with Kevin's patch, we should be able to happily use cherry-pick
greg0ire
Le 03/03/2016 22:30, Junio C Hamano a écrit :
greg0ire writes:
Steps to repro
Oh great, glad to see that, good job!
greg0ire
Le 03/03/2016 22:17, Kevin Daudt a écrit :
On Tue, Mar 01, 2016 at 12:01:53PM +0100, greg0ire wrote:
Hello,
using git 2.1.4 here, and it seems there is no option to bypass pre-commit
hooks while cherry-picking, while git commit provides a --no-ve
12 matches
Mail list logo
