git fetch git log ..origin -- Shawn. --

The description for core.autocrlf refers to reads from / writes to the "filesystem". While the term is used elsewhere in the config documentation to refer to the filesystem git is hosted on, it is not only less clear from context in the case of core.autocrlf, but can also be plain inaccurate in many cases. To make more clear the direction of removal / addition of CR when core.crlf is set, as well as to account for the usage of low-level commands such as hash-object or cat-file, we change ...

[Mostly I'm sending this so I can add a "TODO" label to it in my gmail.] :-) With modern git, setting up a remote bare repo that you can push to is finally down to a reasonable number of commands: $ ssh remote git init --bare myproject.git $ git remote add -m master origin remote:myproject.git $ git push -u origin master But we can do better. I was thinking something like: $ git remote init [--push] [--mirror] <name> <ssh_url> This would perform all of the steps above, except for the ...

The default for gc.aggressiveWindow has been 250 since 1c192f3 (gc --aggressive: make it really aggressive, 2007-12-06). Signed-off-by: Jay Soffian <jaysoffian@gmail.com> --- Documentation/config.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Documentation/config.txt b/Documentation/config.txt index 06b2f82..aa5411e 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -914,7 +914,7 @@ format.signoff:: gc.aggressiveWindow:: The window ...

What git version are you using? It seems to work for me: $ mkdir s $ cd s $ git init $ echo a > a $ git add a $ git commit -m i $ cd .. $ git clone -s s c $ cd c $ git repack -a $ mv .git/objects/info/alternates .git/objects/info/alternates.orig $ git branch * master

On Tue, Apr 13, 2010 at 6:23 PM, Ilari Liusvaara I think it's better to put all output-* files in a separate directory. --

Hi, Most of the time, I run git rebase with -i, so while it is slow, I always assumed there was somehow a reason. For some reason, today, I was running some git rebase without -i, and then the same rebases with -i, but without changing the pick list. While the git rebase without -i were almost instant, git rebase -i was as slow as usual, which is very far from instant. Has anyone else seen such behaviour ? Mike --

Hello We've run into something we'd like to do with "git svn clone" that looks like it should work, but doesn't appear to. The task: we have an SVN repository with 38 modules in it (each with their own branches, tags, and trunk) and we'd like to pull just two of the modules into a single git repository -- but maintain the ability to perform git svn rebase/fetch/dcommit as the SVN repository is remaining active for some developers. It looks like we should be able to point at the parent of ...

Right, that will be why :-). No problem, apologies for not catching the earlier discussion. It's good to hear that you have collectively reached a very similar design to the one indicated from my perforce importer experiment (SVN is of course, a poor imitation of Perforce in No problem at all. I will watch the development of this project with interest. All the best, Sam --

Hi, How do I go about getting the latest list of branches and tags with git svn? My list seems to basically stay at the same state as when I initially created the repo. Subsequent git svn rebase and git svn fetch operations seem to just be fetching changes to trunk. Thanks, Kevin --

On the second look, there's another case, when RUN_SETUP_GENTLY is set, but no repository is found. git_config() will pick $(cwd)/.git/config if it exists. I guess it's OK for this series because the true fix will require more changes. -- Duy --

This still leaves a chance of going wrong: when user explicitly gives "--paginate", use_pager will be 1, but commands like "git init" does not have RUN_SETUP*. So when setup_pager is called later on, it will mess things up. This could be solved completely (indeed I have a patch under testing), but it would require unset_git_directory(), making this series a bit longer :( -- Duy --

These patches are designed to make people who want the pager.<cmd> configuration to be more reliable a little happier. More importantly, they bring the setup procedure closer to doing the Right Thing™. More precisely: The pager configuration procedure does not always do as much as one would like: A. Unless one runs check_pager_config() first, the pager.<cmd> configuration is ignored. The setup procedure does not run check_pager_config() for commands that do not use RUN_SETUP. B. ...

From: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> If git is passed the --paginate option, committing the pager choice will require setting up a pager, which requires access to repository for the core.pager configuration. After handle_options() is called, the repository has not been searched for yet. Unless GIT_DIR or GIT_CONFIG is set, attempting to access the configuration at this point results in git_dir being set to .git, which is almost certainly not what was wanted. If a git command ...

From: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> The startup_info struct will collect information managed by the git setup code, such as the prefix for relative paths passed on the command line (i.e., path to the starting cwd from the toplevel of the work tree) and whether a git repository has been found. In other words, startup_info is intended to be a collection of global variables representing results that were previously returned from setup functions. Letting these values persist means ...

From: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Attempts to access gitdir are everywhere, even before cmd_*() is called (examples: alias handling, pager configuration, work tree). Because the repository has not been found, repository-specific information (i.e., $GIT_DIR/config) can not be read. This leads to obscure bugs. So the sooner we setup gitdir, the less trouble we may have to deal with. This patch sets up the infrastructure. Later patches will teach particular commands to use it ...

I was thinking of sending the remainder of nd/setup after this to save others the trouble of rebasing, but I fear the traffic would be too disruptive. So I am putting it up by git. Caveats: maybe these patches make no sense. After I last rebased them, I walked away without looking. Still, maybe they can save you some time. Good night, Jonathan The following changes since commit e0cc2322c409c6cfa897f395f6feb058e2d53d4a: Nguyễn Thái Ngọc Duy (1): config: run setup before ...

On Tue, 13 Apr 2010 12:43:51 +0300, Ilari Liusvaara Yes. I intend to revist the header and documentation, as they were mostly I think that it probably makes sense to have explicit calls into the backend for start and end rather than assuming that wrapping everything in an object is appropriate, an XML backend for example could then use those callbacks to do XML headers and the outmost element tags etc. -- Julian --

IMHO this "noop" behavior seems to be identical to "git reset --hard master" - the result is the same. Frankly, I don't understand what is useful in such thing being HIDDEN in "incorrect call" of interactive rebase... Thanks, Eugene --

Move duplicate maildomain checks to a single subroutine. Require that a FQDN contains at least one period. Signed-off-by: Jari Aalto <jari.aalto@cante.net> --- git-send-email.perl | 21 +++++++++++++++++---- 1 files changed, 17 insertions(+), 4 deletions(-) Here is improved version. -- Jari >Re: [PATCH 1/3] send-email: Don't use FQDNs without a '.' >Junio C Hamano <gitster@pobox.com> writes: >> Brian Gernhardt <brian@gernhardtsoftware.com> writes: > >> ...

Ugh. I didn't even know we had such a thing. Those look like the only ones that should be a problem, though. I'm glad to have factored out the Should this perhaps be: if (*placeholder == '+' || *placeholder == '-') placeholder++; switch (*placeholder) { case 'N': w->notes = 1; break; } so that it will extend naturally if other placeholder lookups are needed (since those ones also could have + or - markers). Also, I just noticed that your case is missing a 'break'. Not ...

This version looks good to me. 1. Style, no whitespace between arguments. 2. That function name also sucks. I doubt it is worth spending more time on, though. -Peff --

From: Johannes Gilger <heipei@hackvalue.de> When using git log --pretty='%N' without an explicit --show-notes, git would segfault. This patches fixes this behaviour by loading the needed notes datastructures if --pretty is used and the format contains %N. When --pretty='%N' is used together with --no-notes, %N won't be expanded. This is an extension to a proposed patch by Jeff King. Signed-off-by: Johannes Gilger <heipei@hackvalue.de> --- Introduced space when calling ...

When using git log --pretty='%N' without an explicit --show-notes, git would segfault. This patches fixes this behaviour by loading the needed notes datastructures if --pretty is used and the format contains %N. When --pretty='%N' is used together with --no-notes, %N won't be expanded. This is an extension to a proposed patch by Jeff King. Signed-off-by: Johannes Gilger <heipei@hackvalue.de> --- Simpler checking of character after %+ and %- for 'N'. Reindentation of 'case' below 'switch' to ...

When using git log --pretty='%N' without an explicit --show-notes, git would segfault. This patches fixes this behaviour by loading the needed notes datastructures if --pretty is used and the format contains %N. When --pretty='%N' is used together with --no-notes, %N won't be expanded. This is an extension to a proposed patch by Jeff King. Signed-off-by: Johannes Gilger <heipei@hackvalue.de> --- Shifted responsibility for zeroing the userformat_want struct to the caller after Junio ...

In exec_cmd.c, git hard-codes a default path of /usr/local/bin:/usr/bin:/bin. Get an appropriate value for the system from <paths.h> if possible instead. We only try to include <paths.h> on Linux, FreeBSD, NetBSD, OpenBSD and GNU where it is known to exist. Signed-off-by: Chris Webb <chris@arachsys.com> --- Makefile | 10 ++++++++++ exec_cmd.c | 2 +- git-compat-util.h | 6 ++++++ 3 files changed, 17 insertions(+), 1 deletions(-) diff --git a/Makefile ...

Perhaps. OTOH I just noticed I could also drop the NULL (and let the implicit 0-padding take over) which makes every style fit on a single No, thanks for catching this. -- Thomas Rast trast@{inf,student}.ethz.ch --

We use this patch-series in our buildsystem, where we just now tagged about 14 projects as stable (on top of an earlier beta tag). Everything's working just fine, so... Tested-By: Andreas Ericsson <ae@op5.se> Thanks a lot, Shawn. -- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should ...

Surely I can, but I am curious as to the motivation behind '1 second' in the original patch. If you wanted to give these '1 second' ones slight preference over the ones with 'date stamp at the UNIX epoch', that logic is not there anymore in the re-rolled series, no? --

Thanks a lot for noticing this bug. GITWEB_JS and GITWEB_CSS were originally meant to be URI to file with gitweb JavaScript code and default gitweb stylesheet,... but during work on minification of JavaScript code and CSS file it somehow got confused to mean source path. If I remember correctly the original patch, before adding required support for minified gitweb.js and gitweb.css to git-instaweb script, and before support for CSS minification had ifdef JSMIN gitweb.cgi: ...

I would prefer if Git would simply "not refuse," but barring that, a more verbose error would be helpful. I knew what I was doing in http://github.com/jelmer/dulwich/issues/issue/17, but it took me a long time to even notice git's message. --