Documentation for git log --all incorrect

The help for git log --all says: --all Pretend as if all the refs in refs/ are listed on the command line as commit. This makes no sense, as commit is not a documented valid command line parameter. These are the documented parameters: SYNOPSIS

Bug reporting method too hard to find

I could not find out how to report a bug. In the end, a colleague had to tell me. Some suggested improvements: 1) Explicitly mention the word bug on the home page, or have a page which Google will find called Reporting bugs. 2) I did eventually get to the Community page:

Problem with git when rebasing

Hi all, git rebase can sometimes forget a commit, here is the workflow to reproduce this problem: $ git init . $ echo content 1 file1 $ git add file1 git commit -m C1 $ echo content 2 file2 $ git add file2 git commit -m C2 $ echo content 3 file3 $ echo content 2.3 file2 $ git add file3 git

Safe to interrupt »git gc --auto«?

Hi! I couldn't find this answered in the documentation: if, instead of exiting right away, a »git gc --auto« actually commences its housekeeping tasks, is it safe to interrupt (C-c, SIGINT) the original git invocation at this point, or might this cause any inconsistencies, data loss, or failure

[RFC/PATCH] cache-tree: avoid infinite loop on zero-entry tree

The loop in cache-tree's update_one iterates over all the entries in the index. For each one, we find the cache-tree subtree which represents our path (creating it if necessary), and then recurse into update_one again. The return value we get is the number of index entries that belonged in that

Re: [PATCH 05/15] refs.c: update rename_ref to use a transaction

On Tue, Oct 28, 2014 at 2:12 PM, Junio C Hamano gits...@pobox.com wrote: Ronnie Sahlberg sahlb...@google.com writes: I timed a git branch -m for a branch with ~2400 log entries and it takes neglible time : real 0m0.008s user 0m0.000s sys 0m0.007s I really hate this line of

Re: [PATCH] use child_process_init() to initialize struct child_process variables

On Tue, Oct 28, 2014 at 09:52:34PM +0100, René Scharfe wrote: --- a/bundle.c +++ b/bundle.c @@ -381,7 +381,7 @@ int create_bundle(struct bundle_header *header, const char *path, write_or_die(bundle_fd, \n, 1); /* write pack */ - memset(rls, 0, sizeof(rls)); +

[PATCH] git-imap-send: use libcurl for implementation

Resending this once more, as indicated by xmqqbnp4hu8g@gitster.dls.corp.google.com Hope my formatting and posting style is now conformant. Sorry for the noise. Am 2014-08-27 um 19:20 schrieb Junio C Hamano: Bernhard Reiter ock...@raz.or.at writes: [...] For now, the old ones are wrapped

Re: [PATCH 05/15] refs.c: update rename_ref to use a transaction

Ronnie Sahlberg sahlb...@google.com writes: On Tue, Oct 28, 2014 at 2:12 PM, Junio C Hamano gits...@pobox.com wrote: More importantly, when you know that the end result you want to see is that the old and new log files are bit-for-bit identical, and if not there is some bug in either parsing

Is there way to set git commit --date to be older than 1970 ?

Hello all, I am playing with git in slightly unusual manner - e.g., to use git to store history of europe: $ touch Italy $ git add Italy $ git commit -m add Italy --date=01/01/1861T01:01:01 # Italy gained sovereignity at year 1861 fatal: invalid date format: 01/01/1861T01:01:01 It seems the

Re: [RFC/PATCH] cache-tree: avoid infinite loop on zero-entry tree

Jeff King p...@peff.net writes: I'm a little iffy on this just because it is fixing one particular bug, and I am sure there are probably a bunch of other ways to have a bogus index. Fundamentally, I think we pretty much trust that the index was not maliciously generated (unlike packfiles, for

Re: [RFC/PATCH] cache-tree: avoid infinite loop on zero-entry tree

On Wed, Oct 29, 2014 at 11:50:12AM -0700, Junio C Hamano wrote: Jeff King p...@peff.net writes: I'm a little iffy on this just because it is fixing one particular bug, and I am sure there are probably a bunch of other ways to have a bogus index. Fundamentally, I think we pretty much

Re: Is there way to set git commit --date to be older than 1970 ?

On Wed, Oct 29, 2014 at 07:49:19PM +0100, Peter Vojtek wrote: I am playing with git in slightly unusual manner - e.g., to use git to store history of europe: Actually you're the second person I hear that is trying to use git as a timeline of some sort. The previous person had the exact same

Re: [PATCH] use child_process_init() to initialize struct child_process variables

Jeff King p...@peff.net writes: On Tue, Oct 28, 2014 at 09:52:34PM +0100, René Scharfe wrote: --- a/bundle.c +++ b/bundle.c @@ -381,7 +381,7 @@ int create_bundle(struct bundle_header *header, const char *path, write_or_die(bundle_fd, \n, 1); /* write pack */ -

Re: Regression and failure to clone/fetch with new code Re: git-svn performance

Hin-Tak Leung ht...@users.sourceforge.net wrote: Hi, I patched my system git with the recent git-svn improvements, and just use it for general use; so theses are the patches, against 2.1.0. 0001-git-svn-only-look-at-the-new-parts-of-svn-mergeinfo.patch

Re: Is there way to set git commit --date to be older than 1970 ?

Peter Vojtek peter.voj...@gmail.com writes: It seems the commit date can be between 1970 and 2100 (on my 32bit linux),... The underlying data representation records time as number of seconds since epoch (1970-01-01). Theoretically the codepaths that read data could consider negative

[PATCH] Git.pm: add specified name to tempfile template

This should help me track down errors in git-svn more easily: write .git/Git_XX: Bad file descriptor at /usr/lib/perl5/SVN/Ra.pm line 623 Signed-off-by: Eric Wong normalper...@yhbt.net --- Not sure you want to take this separately or in a git-svn pull. Still working on

Re: [PATCH] Git.pm: add specified name to tempfile template

Eric Wong normalper...@yhbt.net writes: This should help me track down errors in git-svn more easily: write .git/Git_XX: Bad file descriptor at /usr/lib/perl5/SVN/Ra.pm line 623 Signed-off-by: Eric Wong normalper...@yhbt.net --- Not sure you want to take this separately

Re: Is there way to set git commit --date to be older than 1970 ?

thanks for quick response, Fredrik. I'm curious, why did you choose git for this? Maybe this is a use case we should consider? this is a part of thinking out of the box mental execise. With the advent of many tools to visualize and analyze git repositories, it makes some sense to use the

Re: Documentation for git log --all incorrect

On Wed, Oct 29, 2014 at 11:51:34AM +, Francis Irving wrote: The help for git log --all says: --all Pretend as if all the refs in refs/ are listed on the command line as commit. This makes no sense, as commit is not a documented valid command

[PATCH] git-svn: prepare SVN::Ra config pieces once

Memoizing these initialization functions saves some memory for long fetches which require scanning many unwanted revisions before any wanted revisions happen. Signed-off-by: Eric Wong normalper...@yhbt.net --- perl/Git/SVN/Ra.pm | 63 +++--- 1 file

Re: Is there way to set git commit --date to be older than 1970 ?

Peter, You should be happy of getting the error message. Since Git 2 invalid years will default to the current year (keeping the given day and month) without warnings. -- Roberto Decurnex On Wed, Oct 29, 2014 at 4:31 PM, Junio C Hamano gits...@pobox.com wrote: Peter Vojtek

[ANNOUNCE] Git v2.1.3

The latest maintenance release Git v2.1.3 is now available at the usual places. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public repositories all have a copy of the 'v2.1.3' tag and the 'maint' branch that the tag points at: url =

Re: Bug reporting method too hard to find

On Wed, Oct 29, 2014 at 11:58:57AM +, Francis Irving wrote: I could not find out how to report a bug. In the end, a colleague had to tell me. Thanks for your suggestions; they all seem like improvements. I just opened: https://github.com/git/git-scm.com/pull/462 which implements most

Re: Safe to interrupt »git gc --auto«?

Thomas Schwinge wrote: I couldn't find this answered in the documentation: if, instead of exiting right away, a »git gc --auto« actually commences its housekeeping tasks, is it safe to interrupt (C-c, SIGINT) the original git invocation at this point, or might this cause any inconsistencies,

Re: [PATCH] git-imap-send: use libcurl for implementation

Bernhard Reiter ock...@raz.or.at writes: Resending this once more, as indicated by xmqqbnp4hu8g@gitster.dls.corp.google.com Hope my formatting and posting style is now conformant. Sorry for the noise. Thanks. The patch does not apply for me (please send a trial message to yourself and

Re: Regression and failure to clone/fetch with new code Re: git-svn performance

Argh, sorry. I thought I included the info but I didn't. git 2.1.0 + 10 patches aborts after trunk@28923 (i.e. failing to fetch 28924); if I revert the patches in that order (#5,#4,#2, #1) and retry in the middle, I have to revert all 4 to get 'git svn fetch' to continue on to 28924. I tried

Re: differences between old clone and new Re: git-svn performance

Hin-Tak Leung ht...@users.sourceforge.net wrote: On Tue, 28/10/14, Eric Wong normalper...@yhbt.net wrote: So both merges are correct, but we lose one, and gain one? I'll try to check more closely tomorrow.  Can you point out the exact revisions in the R repo?  Thanks. The

Re: Regression and failure to clone/fetch with new code Re: git-svn performance

Hin-Tak Leung ht...@users.sourceforge.net wrote: Argh, sorry. I thought I included the info but I didn't. Thanks. I'll try a different version of svn later. What do you think were missing in my e-mails? I was skimming and missed the part about Debian packages :) -- To unsubscribe from this

Re: differences between old clone and new Re: git-svn performance

On Thu, 30/10/14, Eric Wong normalper...@yhbt.net wrote: The missing merge on branch R-2-14-branch is: commit 93af4d4cc3a5e0039944dd4e340d26995be8a252 Merge: 121990f 6ff1b87 Author: ripley ripley@00db46b3-68df-0310-9c12-caf00c1e9a41

Re: Regression and failure to clone/fetch with new code Re: git-svn performance

Here is the data dumper info . I tried the dumper code on the R repo as well, and saw that against the virtual box repo, there is one curious difference - $self-{last_rev} is a string rather than a number. I tried hacking around doing $x += 0; to coerce last_rev to a number at various places but