On the Linux kernel repository, doing "git shortlog v2.6.18.." works fine. "git shortlog v2.6.17.." works fine. "git shortlog v2.6.16.." also works fine. But "git shortlog v2.6.15.." dies with a segmentation fault. Trying "git log v2.6.15.. | git shortlog" also produces the same crash while "git log v2.6.16.. | git shortlog" works fine. The old perl version doesn't have any such issue with those test cases, not even with the whole kernel history. Nicolas -

Ok, this doesn't do the locking either, so on cache misses or expiry, you're still going to be that thundering herd. Also, if you want to be nice to clients, I'd seriously suggest that when you hit in the cache, but it's expired (or it's close to expired), you still serve the cached data back, but you set up a thread in the background (with some maximum number of active threads, of course!) that refreshes the cached entry and then you extend the expiration time so that you won't end up ...

Perhaps git-commit should also accept --exclude=<pattern> option? Would that help? -- Jakub Narebski Warsaw, Poland ShadeHawk on #git -

Note that output of cat piped to anything is almost always a bad programming ;-) Maybe the "git add --interactive" would give you a transcript like this: $ git add --interactive '*.c' '*.h' showing list of modified files... 1) bozbar.c 2) filfre.c 3) frotz.h 4) nitfol.c 5) rezrov.h 6) xyzzy.c 7) yomin.h 8) z.c choice> 2 3 5 6 7 showing list of modified files... 1) bozbar.c 2* filfre.c 3* frotz.h 4) nitfol.c 5* rezrov.h 6* xyzzy.c 7...

Here is the remaining of my queue of stgit issues and ideas noted in the last months. A number of items in the "wishlist" section is really here to spawn discussion. Maybe some of them should end up in the TODO list. bugs: - "show" still shows previous patch, after pushing resulted in empty patch (after solving conflict, when "refresh" then has nothing to do) - "stg import" leaves empty patch on the stack after failed patch application - "push --undo" should restore series order - "import --s...

I know. But this is essential. We _have_ to ignore all the files and subdirectories in the directory which contains the .gitlink file, as these files/subdirectories belong to the submodule. There is no other way. You could try to use a special name for the whole directory with the light-weight checkout, e.g. ".checkout". But then, this is useless for submodules, as for submodules, we want to be able to specify the root directory name of the submodule, as that That is not possible: .gitignore...

Why concatenation? I thought the name would be ID of submodule, and should be just somehow unique. And if concatenation, pehaps some forbidden character inserted between No. I meant /home/user/.../linux to mean searching for /home/user/linux /home/linux /linux but I don't think it is useful. As to relative path matching in any parent directory... well, that differs only in direction (up instead of down) in matching filename in .gitignore when path does not contain / (well, actually it...

Dnia pi

Hi, when I recently thought about submodule support, I had the idea that it is easier to get it by going in small, incremental steps, introducing usefull subfeatures on their on while on it. The following is one outcome of this, a proposal for light-weight checkouts of git branches, without the need to have to full repository in a .git subdirectory, but the just have a file .gitlink is simple as possible, which manages the link to the real repository. Of course, this feature is tailored to s...

Eric Wong wrote: Just one comment: > +

Hi, I have weird problem wit git (1.4.4.2). git --bare clone git://git.kernel.org/pub/scm/git/git.git fetches everything correctly; $ cd /tmp $ git clone /gitroot/home/gitrepo/git remote: Generating pack... remote: Done counting 33527 objects. remote: Deltifying 33527 objects. remote: 100% (33527/33527) done Indexing 33527 objects. remote: Total 33527, written 33527 (delta 23162), reused 33527 (delta 23162) 100% (33527/33527) done Resolving 23162 deltas. 100% (23162/23162) done Ch...

This particular breakage cannot be "last two months", but there was a recent breakage by commit f848718a last week on the 'master' branch. --- Now, I am CLUELESS about what MakeMaker does, but would this help? --- diff --git a/perl/Makefile b/perl/Makefile index bd483b0..099beda 100644 --- a/perl/Makefile +++ b/perl/Makefile @@ -29,7 +29,7 @@ $(makfile): ../GIT-CFLAGS Makefile echo ' echo $(instdir_SQ)' >> $@ else $(makfile): Makefile.PL ../GIT-CFLAGS - '$(PERL_PATH_SQ)' $&...

I was to raise the same objection. But this can be solved by using magic _only_ if the template with exception of "modified:" lines matches, and if there is at least one file in "modified:" section. -- Jakub Narebski Warsaw, Poland ShadeHawk on #git -

However, the idea itself is not bad. AFAIK, cogito does it this way. It could be done as separate command, e.g. "git add --interactive", and would only update the index. Josef -

Well, that's why the description says 'the changes to the tracked files' above to make it clear. An obvious alternative is not to talk about staging in terms of `git add` and `git rm` but instead mention `git update-index` in that part of the documentation, but I think that is going backwards. I think the conclusion of recent discussions is not to paper over the differences from new people (nor making git closer to other systems by castrating git), but make things easier to learn for them. My a...

Hi, One of the repositories I have been tracking with git-svn was reorganized and the path that I have been tracking is now in a new location. I was hoping that the following would work: git clone orig new cd new git svn rebuild $NEW_URL I also tried git svn rebuild --remote $NEW_URL This have some output that looked reasonable (svn rev nums and git sha1's). But git svn fetch does nothing and I don't seem to have any of the new content. Am I using this incorrectly? ...

ok, I was lead astray by this part of the doc for rebuild: A Subversion URL may be optionally specified at the command-line if the directory/repository you're tracking has Oh, sorry I didn't find that example. This worked perfectly, thanks! One question: My fingers are in the habit of typing remotes/git-svn. Can I do: cd .git/svn rm -r git-svn mv git-newsvn git-svn Or is there a safer way to rename? Or are there other config-file ways to make this work -- to ...

>

From 105d331aee95c0cf3610ac0d2fd4aa7688bd5211 Mon Sep 17 00:00:00 2001 From: Han-Wen Nienhuys <hanwen@xs4all.nl> Date: Fri, 8 Dec 2006 18:07:56 +0100 GIT can now be built in a separate builddirectory. This is done as follows: mkdir build cd build $my_git_dir/configure make In this case, configure creates an empty directory tree based on the source directory, and wraps Makefiles from source directory in the build directory. The rest of the functionality is delivered with the...

From 6969e092758f65e8b4b3875ab3050cd0c049cc60 Mon Sep 17 00:00:00 2001 From: Han-Wen Nienhuys <hanwen@xs4all.nl> Date: Fri, 8 Dec 2006 18:09:23 +0100 Signed-off-by: Han-Wen Nienhuys <hanwen@xs4all.nl> --- Documentation/Makefile | 33 ++++++++++++++++++++------------- 1 files changed, 20 insertions(+), 13 deletions(-) diff --git a/Documentation/Makefile b/Documentation/Makefile index c00f5f6..51cd707 100644 --- a/Documentation/Makefile +++ b/Documentation/Makefile @@ -1,6 +1,6...

This seems to break existing hooks, or at least old repositories can be stuck using an old version of git-sh-setup in those hooks. You could to add GIT_datadir to PATH before invoking hooks for existing You shoudl probably change these, too: templates/hooks--pre-applypatch:. git-sh-setup templates/hooks--applypatch-msg:. git-sh-setup -- Eric Wong -

Executables should not go to $prefix/share I think. Maybe $prefix/libexec? BTW, I think you touched a larger issue: plumbling/porcelain separation. -- Duy -

Hi, while messing with GIT's build system, I got ** asciidoc -b docbook -d manpage -f ../Documentation/asciidoc.conf ../Documentation/git-tools.txt ERROR: git-tools.txt: line 2: malformed manpage title ERROR: git-tools.txt: line 6: first section must be named NAME ERROR: git-tools.txt: line 9: malformed NAME section body FAILED: /home/lilydev/vc/git/Documentation/git-tools.txt: line 9: unexpected error: ------------------------------------------------------------ Traceback (most recent call l...

Junio's reworking of the git-commit documentation, and the ensuing discussion about what is commited, and how do you select that, made me remember how much I liked SVK -- particularly, how much I liked to remove files from the commit message template, and have them removed from the commit. At first, I thought "great opportunity to contribute my first patch to git", until I realized that git-commit is written in bash, and my brain refuses to understand that. Yep, I'm that bad. So I'm writing this, an...

>