The '--no-xmailer' option is a Getopt::Long boolean option. The
'--no-' prefix (as in --no-xmailer) for boolean options is not
supported in Getopt::Long version 2.32 which was released with Perl 5.8.0.
This version only supports '--no' as in '--noxmailer'. More recent
versions of Getopt::Long, suc
Valery Yundin wrote:
> Hi,
>
> Your patch seems to fix the problem.
> I tried several times and I can svn clone the whole repository in one
> go without a crash.
Thanks for the confirmation. Cc-ing a few other folks who encountered
this problem (and Bcc-ing some folks who emailed me privately).
Hi,
Your patch seems to fix the problem.
I tried several times and I can svn clone the whole repository in one
go without a crash.
Thanks,
Valery
On 30 January 2015 at 01:22, Eric Wong wrote:
> Valery Yundin wrote:
>> Hi,
>>
>> Here you go:
>> dfa72fdb96befbd790f623bb2909a347176753c2 is the fi
Valery Yundin wrote:
> Hi,
>
> Here you go:
> dfa72fdb96befbd790f623bb2909a347176753c2 is the first bad commit
Thank you. Can you give the following patch a try?
I have not been able to reproduce the problem on my end.
If it doesn't work out, I might be out of ideas for a bit :/
Increasing --lo
Hi,
Here you go:
dfa72fdb96befbd790f623bb2909a347176753c2 is the first bad commit
commit dfa72fdb96befbd790f623bb2909a347176753c2
Author: Eric Wong
Date: Fri Oct 24 22:53:52 2014 +
git-svn: reload RA every log-window-size
Despite attempting to use local memory pools everywhere we
By default, a patch that affects outside the working area is
rejected as a mistake; Git itself never creates such a patch
unless the user bends backwards and specifies nonstandard
prefix to "git diff" and friends.
When `git apply` is used without either `--index` or `--cached`
option as a "better
Valery Yundin wrote:
> Tested on:
> git-svn version 2.3.0.rc2 (svn 1.8.11) - FAIL
> git-svn version 2.2.2 (svn 1.8.10) - FAIL
> git-svn version 1.8.4.5 (svn 1.8.11) - WORKS
Thank you for that info. Do you think you can bisect which
versions/revisions of git-svn introduced that failure for us? I
On Thu, Jan 29, 2015 at 12:45 PM, Junio C Hamano wrote:
> +
> +test_expect_success SYMLINKS 'do not follow symbolic link (same input)' '
> +
> + # same input creates a confusihng symbolic link
s/confusihng/confusing/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the
Hi,
Looks like there might be a bug in SVN import code. Here is the
command that fails
> git svn clone --username anonymous
> svn://powhegbox.mib.infn.it/trunk/POWHEG-BOX
r217 = 2e6cdb1f4604b2256195590fa8275632971eac42 (refs/remotes/git-svn)
M lhefread.f
M Z_plus_jet
On Thu, Jan 29, 2015 at 3:26 PM, Junio C Hamano wrote:
> Subject: Documentation/git-remote.txt: stress that set-url is not for
> triangular
>
> It seems to be a common mistake to try using a single remote
> (e.g. 'origin') to fetch from one place (i.e. upstream) while
> pushing to another (i.e. y
Because Git tracks symbolic links as symbolic links, a path that has
a symbolic link in its leading part (e.g. path/to/dir/file, where
path/to/dir is a symbolic link to somewhere else, be it inside or
outside the working tree) can never appear in a patch that validly
applies, unless the same patch
Dick writes:
> I guess the git remote set-url --push command should contain some warning
> about this.
Perhaps something like this would be good enough for a starter.
-- >8 --
Subject: Documentation/git-remote.txt: stress that set-url is not for triangular
It seems to be a common mistake to t
Thanks Junio! I should use git config remote.pushDefault thanks for pointing
me in the right direction.
I guess the git remote set-url --push command should contain some warning
about this.
gr
Dick
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to ma
Dick writes:
> rm -rf left/ right/ right.git/
> git init left
> cd left/
> echo "hello world" > test.txt
> git add test.txt
> git commit -m .
> cd ..
> git clone --bare left right.git
> git clone right.git/ right
> cd right
> git remote set-url origin ../left
> git remote set-url origin --push .
"Tom G. Christensen" writes:
> On 29/01/15 16:43, Jeff King wrote:
>
>> Another option is to just declare that version old and broken, and skip
>> the tests (either by checking its version, or just checking after we
>> import the keys that we can actually _use_ them).
>>
> That would seem a bit h
On Fri, Jan 30, 2015 at 6:27 AM, Chris Packham wrote:
> Hi,
>
> On Thu, Jan 29, 2015 at 8:49 AM, Dick wrote:
>> Hi all,
>>
>> I've encountered a problem with the Dictator and Lieutenants Workflow. I've
>> configured remote origin so it pulls from the "blessed repository" and
>> pushes to the "dev
On 29/01/15 16:43, Jeff King wrote:
Weird. The pubkeys are there in keyring.gpg; I wonder why the older
version of gpg has trouble extracting them (and how one was _supposed_
to export secret keys at that time).
Importing the unmodified keyring.gpg with 1.2.6 yields this:
$ gpg --homedir "$GNU
Hi,
On Thu, Jan 29, 2015 at 8:49 AM, Dick wrote:
> Hi all,
>
> I've encountered a problem with the Dictator and Lieutenants Workflow. I've
> configured remote origin so it pulls from the "blessed repository" and
> pushes to the "developer public" repository.
>
> When the "blessed repository" has
When using the exclude pattern, ^, the completion did not work.
This enables completion after ^ in the same way that completion after ..
is done.
Signed-off-by: Trygve Aaberge
---
contrib/completion/git-completion.bash | 4
1 file changed, 4 insertions(+)
diff --git a/contrib/completion/gi
Please read my bleow email for a transfer offer of 6.5 Million Euro
--
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 Thu, Jan 29, 2015 at 02:30:57PM +0100, Tom G. Christensen wrote:
> On 28/01/15 00:35, Junio C Hamano wrote:
> >A release candidate Git v2.3.0-rc2 is now available for testing
> >at the usual places.
> >
>
> Commit 2cf770 added testing of the --[no-]xmailer option to git send-email
> in t9001-s
On Thu, Jan 29, 2015 at 10:43:20AM -0500, Jeff King wrote:
> It feels a bit hacky, and I wish I knew more about why the current file
> doesn't work (i.e., if we did "gpg --export-secret-keys" with v1.2.6,
> would it produce different output that can be read by both versions?).
> Another option is
On Thu, Jan 29, 2015 at 02:11:05PM +0100, Tom G. Christensen wrote:
> All signed commit tests fail on RHEL4 which is a regression from 2.2.2.
>
> From t4202.42:
>
> ++ git tag -s -m signed_tag_msg signed_tag
> gpg: key CDDE430D: secret key without public key - skipped
> gpg: skipped `C O Mitter
Hello,
I'm trying to set up some navigation shortcuts I have become accustomed to
using in Windows environments, as well as KDE Konsole. I would like to bind
CTRL+Left to "backward-word" and CTRL+Right to "forward-word" (there are
more, but this is a start). I can enable this behavior by adding s
On 28/01/15 00:35, Junio C Hamano wrote:
A release candidate Git v2.3.0-rc2 is now available for testing
at the usual places.
Commit 2cf770 added testing of the --[no-]xmailer option to git
send-email in t9001-send-email.sh
Unfortunately it used the modern Getopt::long style of --no- to
nega
On 28/01/15 00:35, Junio C Hamano wrote:
A release candidate Git v2.3.0-rc2 is now available for testing
at the usual places.
All signed commit tests fail on RHEL4 which is a regression from 2.2.2.
From t4202.42:
++ git tag -s -m signed_tag_msg signed_tag
gpg: key CDDE430D: secret key withou
On 28/01/15 00:35, Junio C Hamano wrote:
A release candidate Git v2.3.0-rc2 is now available for testing
at the usual places.
Building is broken on RHEL4 which is a regression from 2.2.2.
The makefile check for curl >= 7.34.0 fails and enables
USE_CURL_FOR_IMAP_SEND even though curl is 7.12.
Dear Prof.
This email acts as an invitation to our March 15-17, 2015 conferences
in Austria, Vienna. Along with the conference proceedings book, CD and
E-library, as an invited participant, our 36 SCI/ISI indexed journals
will be available to you to publish the extended version of your
papers.
In
28 matches
Mail list logo
