Re: Fwd: Runaway git remote if group definition contains a remote by the same name

On Mon, Dec 30, 2013 at 11:10:31AM -0800, Junio C Hamano wrote: So I think the sanest thing is probably: 1. Teach fetch to expand recursively in a single process, and then tell sub-processes (via a new command-line option) not to expand any further. 2. Teach fetch to

Re: aborted 'git fetch' leaves workspace unusable

Junio C Hamano gits...@pobox.com writes: stephen_le...@stephe-leake.org writes: That left the workspace unusable: - .git/FETCH_HEAD is empty that causes 'git rev-parse FETCH_HEAD' to fail with a confusing error message. This is not limited to your Cygwin environment. I can see

Re: [PATCH 0/3] t0000 cleanups

On Mon, Dec 30, 2013 at 10:51:25AM -0800, Jonathan Nieder wrote: I think it can be better, since the commit message left me scratching my head while the patch itself seems pretty simple. How about something like the following? I am fine with that format, though... Analysis and fix:

Re: [PATCH 1/2] merge-base: fix duplicates and not best ancestors in output

Hello, Junio! Hi there! First of all: I'm new to mailing-lists, sorry if I'm doing it wrong. I've found a bug in git merge-base, causing it to show not best common ancestors and duplicates under some circumstances (example is given in attached test case). Attached??? Sorry about this. I

[PATCH] gc: notice gc processes run by other users

Since 64a99eb4 git gc refuses to run without the --force option if another gc process on the same repository is already running. However, if the repository is shared and user A runs git gc on the repository and while that gc is still running user B runs git gc on the same repository the gc

Re: [PATCH] gc: notice gc processes run by other users

On Tue, Dec 31, 2013 at 7:07 PM, Kyle J. McKay mack...@gmail.com wrote: Since 64a99eb4 git gc refuses to run without the --force option if another gc process on the same repository is already running. However, if the repository is shared and user A runs git gc on the repository and while that

[PATCH] Add MirBSD support to the build system.

Add an entry into the table of supported OSes. Do not set _XOPEN_SOURCE (contrary to OpenBSD) because that disables the u_short and u_long typedefs, which are used unconditionally in various other header files. Signed-off-by: Benny Siegert bsieg...@gmail.com --- config.mak.uname | 7 +++

Preventing unsigned commit/merge/tag

What's the best way of doing this? I'd prefer this be a pre hook on the server that rejects and the user has to rebase and fix their stuff. Though, if there's some way to make it easier for users not to mess up (other than an alias for everything which I'll probably do anyway) that would be

Re: Preventing unsigned commit/merge/tag

On Tue, Dec 31, 2013 at 12:49:01PM -0500, shawn wilson wrote: What's the best way of doing this? I'd prefer this be a pre hook on the server that rejects and the user has to rebase and fix their stuff. Though, if there's some way to make it easier for users not to mess up (other than an alias

Re: [PATCH/RFC] Introduce git submodule add|update --attach

On Sun, Dec 29, 2013 at 8:49 PM, Francesco Pretto cez...@gmail.com wrote: by default git submodule performs its add or update operations on a detached HEAD. This works well when using an existing full-fledged/indipendent project as the submodule, as there's less frequent need to update it or

Re: [PATCH] gc: notice gc processes run by other users

On Tue, Dec 31, 2013 at 10:07 AM, Kyle J. McKay mack...@gmail.com wrote: Since 64a99eb4 git gc refuses to run without the --force option if another gc process on the same repository is already running. However, if the repository is shared and user A runs git gc on the repository and while