Re: [RFC] Clone repositories recursive with depth 1

On 11 Nov 2015, at 21:09, Stefan Beller wrote: > On Wed, Nov 11, 2015 at 11:19 AM, Stefan Beller wrote: >> On Wed, Nov 11, 2015 at 6:09 AM, Lars Schneider >> wrote: >>> Hi, >>> >>> I have a clean build machine and I want to

[PATCH v2] add test to demonstrate that shallow recursive clones fail

From: Lars Schneider "git clone --recursive --depth 1 --single-branch " clones the submodules successfully. However, it does not obey "--depth 1" for submodule cloning. The following workaround does only work if the used submodule pointer is on the default branch.

[PATCH v1] add test to demonstrate that shallow recursive clones fail

From: Lars Schneider "git clone --recursive --depth 1 --single-branch " clones the submodules successfully. However, it does not obey "--depth 1" for submodule cloning. The following workaround does only work if the used submodule pointer is on the default branch.

Re: [PATCH v2] add test to demonstrate that shallow recursive clones fail

On Thu, Nov 12, 2015 at 1:37 AM, wrote: > From: Lars Schneider > > "git clone --recursive --depth 1 --single-branch " clones the > submodules successfully. However, it does not obey "--depth 1" for > submodule cloning. > > The following

Re: [RFC] Clone repositories recursive with depth 1

+cc Stanislav, who came up with the other thread for passing --remote to git submodule On Thu, Nov 12, 2015 at 1:39 AM, Lars Schneider wrote: >> Notice the other email thread, which suggests to include --remote into the >> call to git submodule update depending on a

Re: Draft of Git Rev News edition 8

On Sun, Oct 11, 2015 at 5:56 AM, Christian Couder wrote: > On Sun, Oct 11, 2015 at 1:45 AM, Eric Sunshine > wrote: >> On Sat, Oct 10, 2015 at 7:36 PM, Christian Couder >> wrote: >>> A draft of Git Rev News edition

Request: git stash create --include-untracked

Hello, `git stash create` does not accepts the same options that `git stash save` accepts. It would be handy to have `git stash create` accept `-u`/`--include-untracked` and `-a`/`--all`. This would allow a very simple "freeze-the-world-I-have-to-leave emergency backup" command such as

Re: [PATCH] http: fix some printf format warnings on 32-bit builds

On 12/11/15 05:27, Torsten Bögershausen wrote: >>Ah. OK, so %ld for long and %lld for long long, I suppose. > Only if you have a system that's support it. > > Linux does, Windows not. Sure, but I was speculating specifically about Eric's mac (which I have no experience with). > >> Hmm, not

Fw: [git-users] git fsck error - duplicate file entries - different then existing stackoverflow scenarios

A user recently asked an interesting question on the git-users list. I think it warrants attentions of a specialists more hard-core than we're there over at git-users. So I'd like to solicit help if those knowledgeable, if possible. Begin forwarded message: Date: Wed, 11 Nov 2015 14:30:40 -0800

Re: [PATCH] contrib/subtree: unwrap tag refs

Rob Mayoff writes: > diff --git a/contrib/subtree/git-subtree.sh b/contrib/subtree/git-subtree.sh > index 9f06571..b051600 100755 > --- a/contrib/subtree/git-subtree.sh > +++ b/contrib/subtree/git-subtree.sh > @@ -245,7 +245,10 @@ find_latest_squash() > case "$a" in

[PATCH] rebase-i-exec: Allow space in SHELL_PATH

On Windows, when Git is installed under "C:\Program Files\Git", SHELL_PATH will include a space. Fix "git rebase --interactive --exec" so that it works with spaces in SHELL_PATH. Signed-off-by: Fredrik Medley --- git-rebase--interactive.sh | 2 +- 1 file changed, 1

Re: Fw: [git-users] git fsck error - duplicate file entries - different then existing stackoverflow scenarios

On Thu, Nov 12, 2015 at 02:02:10PM +0300, Konstantin Khomoutov wrote: > A user recently asked an interesting question on the git-users list. > I think it warrants attentions of a specialists more hard-core than > we're there over at git-users. > > So I'd like to solicit help if those

Re: Replicating the default "git log" format with a format string.

On Thu, Nov 12, 2015 at 12:55:53AM +, Kannan Goundan wrote: > For our workflow, author dates aren't very useful. I'm looking for a way to > configure Git so that "git log" shows commit dates instead of author dates. > "--pretty=fuller" gets me almost what I want, but I'd like to avoid the >

Re: [PATCH] Documentation: make formatting more consistent

On Wed, Nov 11, 2015 at 04:41:06PM -0500, Jeff King wrote: > I know we've discussed this particular spot before, and I think there > may have been some disagreement about which style was the best. But > since clearly no patch came out of the last discussion, and since > an inconsistent set of

Re: [PATCH] allow hooks to ignore their standard input stream

On Wed, Nov 11, 2015 at 03:42:22PM +0100, Clemens Buchacher wrote: > On Wed, Nov 11, 2015 at 03:39:20PM +0100, Clemens Buchacher wrote: > > + if (write_in_full(proc.in, buf.buf, buf.len) < 0) { > > + /* We do not mind if a hook does not read all refs. */ > > +

Re: [PATCH] allow hooks to ignore their standard input stream

On Wed, Nov 11, 2015 at 03:39:20PM +0100, Clemens Buchacher wrote: > Since ec7dbd145 (receive-pack: allow hooks to ignore its standard input > stream) the pre-receive and post-receive hooks ignore SIGPIPE. Do the > same for the remaining hooks pre-push and post-rewrite, which read from > standard

Re: [PATCH] rebase-i-exec: Allow space in SHELL_PATH

On Fri, Nov 13, 2015 at 07:03:19AM +0100, Fredrik Medley wrote: > On Windows, when Git is installed under "C:\Program Files\Git", SHELL_PATH > will include a space. Fix "git rebase --interactive --exec" so that it > works with spaces in SHELL_PATH. > > Signed-off-by: Fredrik Medley

GitGui: get rid of information popup window

Hi Git people This popup saying that "No difference has been detected" is little bit boring and useless since it states that an automatic resync will be started and there is no way to stop the resync. Can GitGui remove this popup? Thanks -- To unsubscribe from this list: send the line

Re: [PATCH 0/7] contrib/subtree: Testsuite cleanup

On Thu, Nov 12, 2015 at 08:32:29PM -0600, David Greene wrote: > Sending again with a proper From: address after rebasing on latest master. > > Copying the maintainers because the origin patchset didn't get any > comments and I'm unsure of how to proceed. That's because Junio is on vacation and

[PATCH] contrib/subtree: unwrap tag refs

From: Rob Mayoff If a subtree was added using a tag ref, the tag ref is stored in the subtree commit message instead of the underlying commit's ref. To split or push subsequent changes to the subtree, the subtree command needs to unwrap the tag ref. This patch makes it do so.

Re: [PATCH] contrib/subtree: unwrap tag refs

On Thu, Nov 12, 2015 at 10:36:16PM -0600, David A. Greene wrote: > > + sub="$(git rev-parse "$b^0")" || die "could not > > rev-parse split hash $b from commit $sq" > > This seems like odd quoting. Would not this do the same? > >

Re: [PATCH v2] add test to demonstrate that shallow recursive clones fail

On Thu, Nov 12, 2015 at 10:37:41AM +0100, larsxschnei...@gmail.com wrote: > From: Lars Schneider > > "git clone --recursive --depth 1 --single-branch " clones the > submodules successfully. However, it does not obey "--depth 1" for > submodule cloning. > > The

[PATCH 7/7] contrib/subtree: Handle '--prefix' argument with a slash appended

From: Techlive Zheng 'git subtree merge' will fail if the argument of '--prefix' has a slash appended. Signed-off-by: Techlive Zheng Signed-off-by: David A. Greene --- contrib/subtree/git-subtree.sh | 2 +-

[PATCH 6/7] contrib/subtree: Make each test self-contained

From: Techlive Zheng Each test runs a full repository creation and any subtree actions needed to perform the test. Each test starts with a clean slate, making debugging and post-mortem analysis much easier. Signed-off-by: Techlive Zheng

[PATCH 4/7] contrib/subtree: Add merge tests

From: Techlive Zheng Add some tests for various merge operations. Test combinations of merge with --message, --prefix and --squash. Signed-off-by: Techlive Zheng Signed-off-by: David A. Greene ---

[PATCH 3/7] contrib/subtree: Add tests for subtree add

From: Techlive Zheng Add some tests to check various options to subtree add. These test various combinations of --message, --prefix and --squash. Signed-off-by: Techlive Zheng Signed-off-by: David A. Greene ---

[PATCH 1/7] contrib/subtree: Clean and refactor test code

From: Techlive Zheng Mostly prepare for the later tests refactoring. This moves some common code to helper functions and generally cleans things up to be more presentable. Signed-off-by: Techlive Zheng Signed-off-by: David A. Greene

[PATCH 5/7] contrib/subtree: Add split tests

From: Techlive Zheng Add tests to check various options to split. Check combinations of --prefix, --message, --annotate, --branch and --rejoin. Signed-off-by: Techlive Zheng Signed-off-by: David A. Greene ---

[PATCH 2/7] contrib/subtree: Add test for missing subtree

From: Techlive Zheng Test that a merge from a non-existant subtree fails. Signed-off-by: Techlive Zheng Signed-off-by: David A. Greene --- contrib/subtree/t/t7900-subtree.sh | 4 1 file changed, 4 insertions(+)

Re: [PATCH] http: fix some printf format warnings on 32-bit builds

Torsten Bögershausen writes: > So whenever a long long is printed, I can warmly recommend to use > > PRId64 PRId64 is not suitable for long long, only for int64_t. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B