On Wed, Nov 6, 2013 at 7:43 AM, Christian Couder
chrisc...@tuxfamily.org wrote:
Of course in the latter case, a command should probably be specified
to tell which value should be used with the key.
For example:
[trailer signoff]
key = Signed-off-by:
if_missing = append
On 22 October 2013 15:31, Pavel Roskin pro...@gnu.org wrote:
Catch exceptions in default_repo(). Catch git.RepositoryException.
This suppresses stack trace in stg pull on detached head and outside
the repository.
Signed-off-by: Pavel Roskin pro...@gnu.org
Thanks. Applied.
Catalin
--
To
Jim Garrison venit, vidit, dixit 05.11.2013 18:16:
I'm doing a one-time migration of an svn project. For historical reasons our
repo layout is weird:
trunk/reporting/reporting_app
tags/something_else
tags/reporting_app-2.3.45
tags/reporting_app-2.4.46
upload-pack has long advertised thin-pack, letting the clients request
these smaller packs. The client however unconditionally assumes that a
server is able to fix thin packs and there is no way of telling the
client that this is in fact not the case.
Make receive-pack advertise 'thin-pack' in
In combination a the previous patch making receive-pack advertise the
thin-pack capability, this allows git to push to a server in a
constrained environment which is not able to fix thin packs while taking
advantage of the feature for servers which can.
Signed-off-by: Carlos Martín Nieto
Hi all,
This comes as a result of the discussion starting at [0] about
git-push assuming that a server will always support thin packs. Most
out there in fact do, but this isn't necessarily the case.
Some implementations may not have support for it yet, or the server
might be running in an
On 2013-11-05 22.22, Johannes Sixt wrote:
Am 05.11.2013 21:45, schrieb Torsten Bögershausen:
On 2013-11-05 20.39, Johannes Sixt wrote:
Thanks for picking this up, please see some minor nits inline,
and git_connect() is at the end
-struct child_process *git_connect(int fd[2], const char
On 2013-11-05 01.00, Ramsay Jones wrote:
On 31/10/13 13:24, Torsten Bögershausen wrote:
On 2013-10-30 22.07, Ramsay Jones wrote:
[ ... ]
Yep, this was the first thing I did as well! ;-) (*late* last night)
I haven't had time today to look into fixing up the msvc build
(or a complete
-Original Message-
From: Michael J Gruber [mailto:g...@drmicha.warpmail.net]
Sent: Wednesday, November 06, 2013 6:03 AM
To: Jim Garrison; git@vger.kernel.org
Subject: Re: git svn clone with funky tags layout
Jim Garrison venit, vidit, dixit 05.11.2013 18:16:
I'm doing a one-time
Christian Couder christian.cou...@gmail.com writes:
To append a s-o-b only if there is no s-o-b already, one would need to use:
[trailer signoff]
key = Signed-off-by:
if_exist = dont_append
if_missing = append
command = echo $GIT_COMMITTER_NAME
Jakub Narębski jna...@gmail.com writes:
Finnerty, James M Mr CTR USA USASOC-SOAR wrote
Jeff King [mailto:p...@peff.net]wrote:
On Tue, Oct 29, 2013 at 11:35:21AM -0500, Finnerty, James M Mr CTR USA
USASOC-SOAR wrote:
Hi. I'm going to attempt to import a git database into Razor which is
Sven Brauch svenbra...@googlemail.com writes:
From 2e7b5aed771faeff654a447346bb0b57570d9569 Mon Sep 17 00:00:00 2001
From: Sven Brauch svenbra...@googlemail.com
Date: Tue, 5 Nov 2013 20:06:21 +0100
Subject: [PATCH] git-cat-file: fix output when format string contains no
variables
Thanks;
On Wed, Nov 06, 2013 at 10:00:57AM -0800, Junio C Hamano wrote:
I think the real problem is that sha1_loose_object_info() is called
by sha1_object_info_extended(), when it does not find a cached or a
packed object, and the callee assumes that it is asked to fill in
only the requested pieces
Matthieu Moy matthieu@grenoble-inp.fr writes:
I don't remember all the discussions on the patch which introduced
the warning, but I don't think it's relevant to digg them before applying the
patch:
If we apply the patch then it is too late to dig them ;-)
* The assumption was that
If you want to GPG sign all your commits, you have to add the -S option
all the time. The commit.gpgsign config option allows to sign all
commits automatically.
Signed-off-by: Nicolas Vigier bo...@mars-attacks.org
---
The option description now suggests using an agent.
Documentation/config.txt
On Wednesday 06 November 2013 10:00:57 Junio C Hamano wrote:
Thanks; first some procedural issues:
Thanks, I will take care of the mentioned points for future submissions.
I think the real problem is that sha1_loose_object_info() is called
by sha1_object_info_extended(), when it does not find
Junio C Hamano gits...@pobox.com writes:
Matthieu Moy matthieu@grenoble-inp.fr writes:
I don't remember all the discussions on the patch which introduced
the warning, but I don't think it's relevant to digg them before applying
the patch:
If we apply the patch then it is too late to
From: Junio C Hamano gits...@pobox.com
Christian Couder christian.cou...@gmail.com writes:
To append a s-o-b only if there is no s-o-b already, one would need to use:
[trailer signoff]
key = Signed-off-by:
if_exist = dont_append
if_missing = append
Carlos Martín Nieto c...@elego.de writes:
Hi all,
This comes as a result of the discussion starting at [0] about
git-push assuming that a server will always support thin packs. Most
out there in fact do, but this isn't necessarily the case.
Some implementations may not have support for it
Christian Couder chrisc...@tuxfamily.org writes:
From: Junio C Hamano gits...@pobox.com
Christian Couder christian.cou...@gmail.com writes:
To append a s-o-b only if there is no s-o-b already, one would need to use:
[trailer signoff]
key = Signed-off-by:
if_exist =
Felipe Contreras felipe.contre...@gmail.com writes:
On Thu, Oct 31, 2013 at 12:26 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
+test_expect_success 'use refspec' '
+ git fast-export --refspec refs/heads/master:refs/heads/foobar master
I just commented out few lines, git diff is fine :
@@ -144,10 +145,10 @@ StartUML || exit 2
SHARES=
if [[ $VICTIMS -eq 1 ]]; then
-# SHARES=/tmp
-# SHARES=$SHARES /mnt/hostfs
-# SHARES=$SHARES /mnt/nfsv2
-# SHARES=$SHARES /mnt/nfsv3
+ SHARES=/tmp
+
On Wed, 2013-11-06 at 12:32 -0800, Junio C Hamano wrote:
I'll queue these for now, but I doubt the wisdom of this series,
given that the ship has already sailed long time ago.
Currently, no third-party implementation of a receiving end can
accept thin push, because thin push is not a
Junio C Hamano gits...@pobox.com writes:
That is true, but does it justify giving a misleading information in
the advice message?
Clearly, yes. Trying to be exhaustive here is not a good idea, we'd end
up rewritting the man page, and then users won't read the message
because it's too long.
On Wed, Nov 06, 2013 at 01:00:42PM -0800, Junio C Hamano wrote:
I didn't think things through, but at the external UI level, I see a
possibility of a nicer way to express the above.
In our push refspec (and export is about pushing what we have), a
colonless refspec A is a short-hand for
Hi,
Christian Couder wrote:
Now has_suffix() returns 1 when the suffix is present and 0 otherwise.
Ok. My only worry is that the function is less discoverable since
its name is so different from prefixcmp(), which might cause someone
to invent yet another postfixcmp.
The old name followed
Carlos Martín Nieto c...@elego.de writes:
On Wed, 2013-11-06 at 12:32 -0800, Junio C Hamano wrote:
I'll queue these for now, but I doubt the wisdom of this series,
given that the ship has already sailed long time ago.
Currently, no third-party implementation of a receiving end can
accept
On Wed, Nov 06, 2013 at 02:25:50PM -0800, Junio C Hamano wrote:
Support in the code isn't always enough. The particular case that
brought this on is one where the index-pack implementation can deal with
thin packs just fine.
This particular service takes the pack which the client sent
Junio C Hamano gits...@pobox.com writes:
Also applying this will have an unpleasant fallout to merging the
endgame patch b2ed944a (push: switch default from matching to
simple, 2013-01-04). The added text needs to be corrected with an
evil merge.
I'd prefer to having worry about such a
On 06.11.2013, at 23:17, Jonathan Nieder jrnie...@gmail.com wrote:
Hi,
Christian Couder wrote:
Now has_suffix() returns 1 when the suffix is present and 0 otherwise.
Ok. My only worry is that the function is less discoverable since
its name is so different from prefixcmp(), which
Max Horn wrote:
Well, unlike suffixcmp, it is transitive, so it could be used for sorting.
It is not antisymmetric.
prefixcmp(foo, foobar) 0
prefixcmp(foobar, foo) == 0
I can see how it's possible to care about the sign of the return
value, but it's equally possible to care
мыслите являться Зрячим? мыслите являться Зрячим? Зрячим являться бессменно
прекрасно. http://goo.gl/sGzLoe
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Nov 6, 2013 at 1:41 PM, Carlos Martín Nieto c...@elego.de wrote:
On Wed, 2013-11-06 at 12:32 -0800, Junio C Hamano wrote:
I'll queue these for now, but I doubt the wisdom of this series,
given that the ship has already sailed long time ago.
Currently, no third-party implementation of
Matthieu Moy wrote:
Junio C Hamano gits...@pobox.com writes:
Specifically:
+ When push.default is set to 'matching', git will push all local
branches\n
+ to the remote branches with the same (matching) name.
invites those who do not read documentation to mistake it with using
an
On Wed, Nov 6, 2013 at 2:54 PM, Jeff King p...@peff.net wrote:
If we instead introduced no-thin, it is more like:
1. Receive-pack starts advertising no-thin (as dictated by
circumstances, as Carlos describes).
2. Send-pack which does not understand no-thin will ignore it and send
Am 07.11.2013 um 00:28 schrieb Jonathan Nieder jrnie...@gmail.com:
Max Horn wrote:
Well, unlike suffixcmp, it is transitive, so it could be used for sorting.
It is not antisymmetric.
prefixcmp(foo, foobar) 0
prefixcmp(foobar, foo) == 0
Right! I wasn't thinkinh :-(
I can
A release candidate Git v1.8.5-rc1 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
005ed6e0e91043d1d9da9a47f0235fdac240269a git-1.8.5.rc1.tar.gz
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'.
The first release candidate 1.8.5-rc1 has been tagged.
As promised/requested, the final steps for 2.0 are in 'next'; they,
together with a
Jonathan Nieder jrnie...@gmail.com writes:
The old name followed the pattern anything-cmp(), which suggests
a general comparison function suitable for e.g. sorting objects.
But this was not the case for suffixcmp().
It's not clear to me that prefixcmp() is usable for sorting objects,
On Wed, Nov 6, 2013 at 3:00 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
On Thu, Oct 31, 2013 at 12:26 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
+test_expect_success 'use refspec' '
+
Junio C Hamano wrote:
... users of for-each-ref format will be _more_ familiar with
formats used by for-each-ref, and it would make a lot more sense to
keep the syntactic resemblance between existing features to show
magic things in for-each-ref and the new feature to show color
(which is
41 matches
Mail list logo
