On Sun, Jul 24, 2016 at 6:07 AM, Jon Forrest wrote:
> This an announcement of Pro Git Reedited 2nd Edition, which is
> a substantial edit of Chacon and Straub's Pro Git 2nd Edition.
> I spent a lot of time tightening it up and maybe clearing
> up some explanations.
>
> The pdf is downloadable at:
On Tue, Oct 20, 2015 at 6:00 PM, Junio C Hamano wrote:
>
> Luke Diamand writes:
>
> > On 20 October 2015 at 11:34, Etienne Girard
> > wrote:
> >> Hello,
> >>
> >> Git-p4 fail when I try to rebase with the error: "NameError: global
> >> name 'ctypes' is not defined". The error occurs when I use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 27/04/2013 21:15, Felipe Contreras ha scritto:
> [...]
>>> @@ -480,7 +481,7 @@ __git_complete_revlist_file ()
>>> # The exception is --committable, which finds the files appropriate commit.
>>> __git_complete_index_file ()
>>> {
>>> - local
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 27/04/2013 15:07, Felipe Contreras ha scritto:
> [...]
> This should do the trick. No?
>
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -262,16 +262,17 @@ __git_ls_files_helper ()
> #If provi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 27/04/2013 12:19, Felipe Contreras ha scritto:
> Hi,
>
> Basically while trying to understand the code for path completion, I found
> that
> a lot of code was duplicated, and for not much gain.
>
> I also noticed that doing 'git add file' doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 21/04/2013 12:14, Felipe Contreras ha scritto:
> On Fri, Jan 11, 2013 at 12:48 PM, Manlio Perillo
> wrote:
>> The git-completion.bash script did not implemented full, git aware,
>> support to complete paths, for git commands tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 02/04/2013 16:32, Matthieu Moy ha scritto:
> Felipe Contreras writes:
>
>> And this is a workaround:
>>
>> --- a/contrib/completion/git-completion.zsh
>> +++ b/contrib/completion/git-completion.zsh
>> @@ -66,7 +66,7 @@ __gitcomp_file ()
>>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 01/04/2013 11:29, Felipe Contreras ha scritto:
>
>
> On Thu, Feb 28, 2013 at 12:59 PM, Manlio Perillo
> mailto:manlio.peri...@gmail.com>> wrote:
>
>
> [1] Basically, on my system I need the following change at th
in contrib/.
>
Using this configuration I still can't reproduce the problem, using
git v1.8.2-rc3-8-g0c91a6f.
But I'm not a zsh expert.
Regards Manlio Perillo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://eni
.g.
>
> result=$(__git_ls_files_helper dir/ args...)
>
> Otherwise the user's shell would have been taken to an unexpected
> place, with or without CDPATH.
>
Right; this is the reason I used the `{` grouping, instead of `(`.
However, since the `{` is already specifie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 11/03/2013 18:01, Junio C Hamano ha scritto:
> [...]
> Having to restrict to the common subset means that whenever bash
> adds new and useful features that this script could take advantage
> of to improve the user experience, they cannot be employed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 11/03/2013 17:17, Junio C Hamano ha scritto:
> Matthieu Moy writes:
>
>> The function-wide redirection used for __git_ls_files_helper and
>> __git_diff_index_helper work only with bash. Using ZSH, trying to
>> complete an inexistant directory gave
ing it from Git.
>
> [...]
> moy@anie:~$ zsh --version
> zsh 4.3.10 (i686-pc-linux-gnu)
>
> (this is ZSH packaged with Debian stable)
>
I have the same system, but I can't reproduce the problem.
What is the content of your .zshrc file?
Regards Manlio Perillo
-BEGIN PGP SIGNATU
guilty commit is fea16b47b60 (Fri Jan 11 19:48:43 2013, Manlio
> Perillo, git-completion.bash: add support for path completion), which
> introduces a new __gitcomp_file function that uses the bash builtin
> "compgen", without redefining the function in git-completion.z
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 02/02/2013 21:10, Junio C Hamano ha scritto:
> Marc Khouzam writes:
>
>> Recent enhancements to git-completion.bash provide
>> intelligent path completion for git commands. Such
>> completions do not add the '/' at the end of directories
>> for r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 30/01/2013 19:55, Marc Khouzam ha scritto:
> [...]
The new logic in git-completion.bash tells bash that 'filenames'
completion is ongoing so bash will add a '/' after directories.
Sadly, tcsh won't do that, so it would be simpler if
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 30/01/2013 15:06, Marc Khouzam ha scritto:
> [...]
>> I will try to update the patch, with your latest suggestions (avoid
>> tricky POSIX shell syntax, and CDPATH issue - if I remember
>> correctly),
>> and with an update for the t/t9902-completion
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 28/01/2013 18:52, Junio C Hamano ha scritto:
> [...]
>
> Thanks both for commenting. I'll find time to read it over again
> and perhaps we can merge it to 'next' and advertise it in the next
> issue of "What's cooking" report to ask for wider test
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 28/01/2013 17:22, Michael J Gruber ha scritto:
> [...]
>> The patch will suggest (for git add command), all the files that are
>> candidate to be added to the index file.
>>
>> Please, test it and report any behaviour you think is incorrect.
>
> OK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 28/01/2013 13:52, Michael J Gruber ha scritto:
> Manlio Perillo venit, vidit, dixit 28.01.2013 10:26:
>> Il 28/01/2013 00:00, Junio C Hamano ha scritto:
>>> wookietreiber writes:
>>
>>>> I have a feature r
hing. I guess it would be much nicer (as in
>> increasing productivity) if it would only suggest unstaged
>> content, as reported by `git status`, because that would be the
>> only content one would be able to add.
>
> I think that is what Manlio Perillo tried to do with the s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
This is not really a bug, but a small usability problem.
When completing a reference, Bash will add a space after the reference name.
As an example in:
$git show master
The problem is that an user may want to show a tree or blog object fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 11/01/2013 23:02, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> +# Process path list returned by "ls-files" and "diff-index --name-only"
>> +# commands, in order to list only file names relati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 11/01/2013 19:48, Manlio Perillo ha scritto:
> The git-completion.bash script did not implemented full, git aware,
> support to complete paths, for git commands that operate on files within
> the current working directory or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 11/01/2013 09:06, Dylan Smith ha scritto:
> Trying to complete the command
>
> git show master:./file
>
> would cause a "Not a valid object name" error to be output on standard
> error. Silence the error so it won't appear on the command line.
>
rd option of the ls-files command.
When using a recent Bash version, Git path completion will be the same
as builtin file completion, e.g.
git add contrib/
will suggest relative file names.
Signed-off-by: Manlio Perillo
---
Changes:
* Applied Junio patch to fix completio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 10/01/2013 12:39, Jeff King ha scritto:
> On Thu, Jan 10, 2013 at 12:17:31PM +0100, Manlio Perillo wrote:
>
>> In the contrib/vim/README file there are instructions about how to setup
>> git support with Vim builtin git syntax fi
HBfUXCl8o
36IAn3t72o/+5R/x1TF7r9mu85z6wY25
=b2l0
-END PGP SIGNATURE-
" Vim syntax file
" Language: git format-patch message
" Maintainer: Manlio Perillo
" Filenames:[0-9]*.patch (first line is "From ... # This line is ignored.")
"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 09/01/2013 21:21, Marc Khouzam ha scritto:
> [...]
>
> $zsh
> synapsis% source contrib/completion/git-completion.zsh
> (anon):6: command not found: ___main
> _git:11: command not found: _default
>
> I have disabled compinit autoload (since, I don'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I have finally resolved all the problems with my path completion in
git-completion.bash and, in order to avoid regressions, I'm checking the
git-completion.zsh and git-completion.tcsh scripts, since they use the
bash completion support.
I have in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 08/01/2013 19:05, John Keeping ha scritto:
> [...]
>>
>> After some searching, I found how this is supposed to be done.
>> It is possible to use the -o filenames option to tell Bash completion
>> that "the compspec generates filenames, so it can per
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/01/2013 21:23, Marc Khouzam ha scritto:
> [...]
> 4- Completion choices include their entire path, which is not what bash does
> by default. For example:
>> cd git/contrib
>> ls completion/git-
> git-completion.bash git-completion.tcsh git-co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/01/2013 21:23, Marc Khouzam ha scritto:
> [...]
> Below are two suggestions that are in line with this effort but that are not
> regressions.
>
> A) It would be nice if
> git commit -a
> also completed with untracked files
>
$ git commit -a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/01/2013 21:23, Marc Khouzam ha scritto:
> [...]
> Thanks for this, it improves the situation dramatically.
> I did further testing with your patch and found some less obvious
> issues. I didn't debug the script myself as I'm not that familiar wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/01/2013 07:27, Junio C Hamano ha scritto:
> Junio C Hamano writes:
>
>> Marc Khouzam writes:
>>
>>> I've been playing with it but I'm not getting the expected
>>> behavior when I cd to a sub-directory.
>>
>> Thanks for testing. Manlio?
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/01/2013 21:23, Marc Khouzam ha scritto:
> [...]
> I did further testing with your patch and found some less obvious
> issues. I didn't debug the script myself as I'm not that familiar with
> it either, but I think the testcases below should help
t_dir variable (used to remember if and
> what git dir should be removed in case of failure) to the new value given
> with the --seperate-git-dir option. Also add a test for this to t5600 (and
> while at it fix the former last test to not cd into a directory to test
> for its existence b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Many C projects I have seen (based on autoconf, but not always - like
Nginx) allow the project to be build in a separate directory, in order
to avoid to pollute the working directory with compiled files.
Unfortunately this seems to not be possibl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/01/2013 15:01, Jens Lehmann ha scritto:
> [...]
>>> $ git submodule update --init
>>> fatal: Needed a single revision
>>> Unable to find current revision in submodule path 'pixman'
>>>
>>> The problem is easy to solve: manually remove the pixman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 04/01/2013 22:51, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> $ git submodule update --init
>> ...
>> Submodule 'roms/vgabios' (git://git.qemu.org/vgabios.git/) registered
>> for path '
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
My network connection at times is rather unstable, so I can experience
all sort of network problems.
Today I tried to clone the qemu repository, and then to update all
submodules.
I'm using git from a recent master (790c83 - 14 December).
This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 21/12/2012 19:17, Junio C Hamano ha scritto:
> [...]
> Of course you can plan ahead (this is what I usually do when working
> on a series that is not "how about this" throw-away patch I send to
> this list all the time) and name the topic "topic-v1"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 21/12/2012 18:59, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> +case "$path" in
>> +?*/*) echo "${path%%/*}/" ;;
>> +*) echo $path ;;
>
> $path un
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 21/12/2012 18:01, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> I would like to have advices about some possible workflows to use when
>> maintaining a patch, that can evolve over the time (fixing bugs, and
>&g
;git commit" command will suggest all
files that have been modified from the HEAD, if HEAD exists, otherwise
it will suggest all cached files.
For all affected commands, completion will always stop at directory
boundary. Only standard ignored files are excluded, using the
--exclude-sta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 20/12/2012 15:13, Eric S. Raymond ha scritto:
> Signed-off-by: Eric S. Raymond
> ---
Just my two cents.
Isn't it better to have some core Python support inside a "python/"
directory in the git source tree (e.g. e simple python/git.py), and have
*a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I would like to have advices about some possible workflows to use when
maintaining a patch, that can evolve over the time (fixing bugs, and
applying advices from reviewers).
In my case I have a single commit to maintain.
The workflow I use now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 19/12/2012 23:49, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>>> git mv COPYING README X
>>
>> Assuming X is a new untracked directory, do you think it is an usability
>> problem if an user try
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 19/12/2012 20:57, Junio C Hamano ha scritto:
> [...]
I just found a serious bug with "git commit" path completion.
When doing the first commit on an empty repository, completion will
cause an error:
$git commit -m init fatal: ambiguous argument '
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 17/12/2012 20:42, Junio C Hamano ha scritto:
> [...]
>>> I am not sure how you would handle the last parameter to "git mv",
>>> though. That is by definition a path that does not exist,
>>> i.e. cannot be completed.
>>
>> Right, the code should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 19/12/2012 20:57, Junio C Hamano ha scritto:
> [jch: again, adding area experts to Cc]
>
> Manlio Perillo writes:
>
>> Changes from version 2:
>>
>> * Perl is no more used.
>> * Fixed some coding
cluded.
* the path completion for the "git commit" command will suggest all
files that have been modified from the HEAD.
For all affected commands, completion will always stop at directory
boundary. Only standard ignored files are excluded, using the
--exclude-standard option of the ls
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 18/12/2012 20:22, Junio C Hamano ha scritto:
> [...]
>> Note that the performance is the reason why I suggested, in a previous
>> email, that git should have some more options to format data in custom ways.
>> As an example, there is no way to tell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 18/12/2012 19:11, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> Documentation seems to suggest this is supported, but it is not true:
>>
>> $ git diff HEAD:git.c HEAD~100:git.c -- gi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 18/12/2012 18:53, Junio C Hamano ha scritto:
> [jch: cc'ed git-completion experts to review implementation details]
>
> Manlio Perillo writes:
>
>> The git-completion.bash script did not implemented full, git aware,
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Documentation seems to suggest this is supported, but it is not true:
$ git diff HEAD:git.c HEAD~100:git.c -- git.c
usage: git diff [] [ []] [--] [...]
unless I'm missing something.
Manlio
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.
nly standard ignored files are excluded, using the
--exclude-standard option of the ls-files command.
Signed-off-by: Manlio Perillo
---
contrib/completion/git-completion.bash | 112 -
1 file changed, 97 insertions(+), 15 deletions(-)
diff --git a/cont
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 17/12/2012 20:42, Junio C Hamano ha scritto:
> [...]
>>> I am not sure how you would handle the last parameter to "git mv",
>>> though. That is by definition a path that does not exist,
>>> i.e. cannot be completed.
>>
>> Right, the code should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 17/12/2012 05:54, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> The git-completion.bash script was using the git ls-tree command
>> without the --name-only option, with a sed filter to parse path names;
>> us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 17/12/2012 05:50, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> The git-completion.bash script did not implemented full support for
>> completion, for git commands that operate on files from the current
>>
d" command is provided using
"git ls-files --exclude-standard -o -m"
* the path completion for the "git clean" command is provided using
"git ls-files --exclude-standard -o"
* the path completion for the "git commit" command is provides using
&q
The git-completion.bash script was using the git ls-tree command
without the --name-only option, with a sed filter to parse path names;
use the --name-only option, instead.
Signed-off-by: Manlio Perillo
---
contrib/completion/git-completion.bash | 15 +--
1 file changed, 1 insertion
d" command is provided using
"git ls-files --exclude-standard -o -m"
* the path completion for the "git clean" command is provided using
"git ls-files --exclude-standard -o"
* the path completion for the "git commit" command is provides using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 16/12/2012 06:59, Junio C Hamano ha scritto:
> I
> Manlio Perillo writes:
>
>> This works with a shell.
>> I'm using Python to write a custom git command.
>
> I would be very surprised if Python lacked a way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 15/12/2012 20:36, Junio C Hamano ha scritto:
> [...]
Unlike other environment variables (e.g. GIT_WORK_TREE,
GIT_NAMESPACE), it was not possible to set the GIT_INDEX_FILE
environment variable using the command line.
>>>
>>> Is this ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 15/12/2012 19:02, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> Unlike other environment variables (e.g. GIT_WORK_TREE,
>> GIT_NAMESPACE), it was not possible to set the GIT_INDEX_FILE
>> environment variabl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 12/12/2012 20:35, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> The Documentation/git.txt file, in the GIT_DIR environment variable
>> section, did not mentioned that this value can also be set using the
>>
adapted from the existing
'using alternate GIT_INDEX_FILE (1)' and
'using alternate GIT_INDEX_FILE (2)' tests.
Signed-off-by: Manlio Perillo
---
Documentation/git.txt | 10 +-
git.c | 17 -
t/t7500-commit.sh | 29 ++
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 12/12/2012 20:35, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> The Documentation/git.txt file, in the GIT_DIR environment variable
>> section, did not mentioned that this value can also be set using the
>>
Unlike other environment variables (e.g. GIT_WORK_TREE, GIT_NAMESPACE),
the Documentation/git.txt file did not mention that the GIT_DIR
environment variable can also be set using the --git-dir command line
option.
Signed-off-by: Manlio Perillo
---
Documentation/git.txt | 1 +
1 file changed, 1
The Documentation/git.txt file, in the GIT_DIR environment variable
section, did not mentioned that this value can also be set using the
--git-dir command line option.
---
Documentation/git.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index
71 matches
Mail list logo
